Extension example parsing

[becky-gilbert]

Fixes #60

@jadeddelta this is my attempt at doing what you suggested here, namely:

first finding all extension mentions, and then doing a catchall for the plugin regex (with deduping)

Any feedback is welcome, but in particular - I'm not entirely sure that I got the intended behavior right. Maybe the first thing to do is have a look at my test example files and the test assertions on each, to see if that's how you think the parser should handle each case? Happy to make changes!

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5dd528a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[jadeddelta]

sorry for the delay, this looks great! i think you basically covered everything i asked for, just broadening the auto-infer process to include objects that mention the extension type. i'll get this merged up, thank you so much again!