Upgrade anchor-markdown-header to fix emoji-titled headers

[kevin-david]

Add test for emoji-titled headers

This provides an example of the problem described in #191.

### Add launch.json to enable test debugging

For codespaces/VS Code. This was very helpful in diagnosing #191.

Based on approach taken in https://stackoverflow.com/a/39607924, though the port stuff wasn't necessary anymore.

Upgrade anchor-markdown-header to fix emoji-titled headers

Actually fixes #191

[thlorenz]

Hi great work @kevin-david on reproducing this in a test.
I'd love if you can take a stab at fixing this as well as I currently don't have bandwidth to address it.
Thanks.

[kevin-david]

Hey @thlorenz this should be fixed by my previous change in thlorenz/anchor-markdown-header#45 - I'm actually using my private fork at the moment, but I would love to clean that up!

We just need a new release of https://www.npmjs.com/package/anchor-markdown-header with that change so I can consume it here, is that something you can do? Happy to update this PR to non-draft mode once that's done (with this test now passing)

[kevin-david]

@thlorenz ready to go now with https://github.com/thlorenz/anchor-markdown-header's 0.6.0 release!

[thlorenz]

Aside from the vscode config file LGTM, so please just remove and we can merge.
I'm making you contrib so you can do this yourself once you fix that nit.

[thlorenz]

Thanks, is this ready to be published to npm?

[kevin-david]

I think so, I've been testing this for a while with my fork and haven't seen any issues!

[thlorenz]

OK went out as v2.2.1. Thanks for your work!

[thlorenz]

Just for the record, I did publish but forgot to check in the version change or tag it.
So unfortunately there is no record of it in the github repo now (I don't have a local copy of it anymore either).

So we just need to be aware the next time we publish a version as npm version patch would again create v2.1.1 which we actually need to skip now.

Sorry about that.