[flutter_markdown]: Invert order of style merging

[domesticmouse]

Fixes: flutter/flutter#81720

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or this PR is exempt from CHANGELOG changes.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[csells]

@navaronbracke: I noticed what a great job you did on flutter/flutter#158428. would you be able to take a look at this one? the recommended fix is in place, but the new test results need to be verified and the tests updated for the new blockquote styling behavor.

[navaronbracke]

@csells If I were to look at this PR, what would be expected of me here? The PR doesn't yet link to an issue that it fixes, so I'm unsure what the expected behavior is. Do you need me to write a test for this PR?

what a great job you did on flutter/flutter#158428

That was only a very small fix, though :p

[csells]

@navaronbracke: actually, I expect this fix to be even smaller. here's the bug report: flutter/flutter#81720

[domesticmouse]

FYI @mit-mit this is an important fix for an upcoming release

[domesticmouse]

@csells, the failing unit test on this PR is flagging that this isn't a complete and proper fix. Can you please take ownership of this fix and do the required investigation in to how to properly fix this issue?

[csells]

This issue isn't blocking but yes, I'll own it ongoing. Thanks for bringing it this far, @domesticmouse

[omar-hanafy]

Any updates here guys?

[csells]

on it!