Hosting.Ngrok - support v2 configuration file with labels

[programmation]

**Closes #446 **

Adds an extra field in NgrokEndpoint to store a dictionary of labels that will be applied to the endpoint in the configuration file.
Also supports output in v2 format. Although this is deprecated it appears to be the only documented way to apply labels to an ngrok endpoint.

PR Checklist

• [x ] Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• [ x] Based off latest main branch of toolkit
• [x ] PR doesn't include merge commits (always rebase on top of our main, if needed)
• New integration
  • Docs are written
  • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• [ x] Tests for the changes have been added (for bug fixes / features) (if applicable)
• [x ] Contains NO breaking changes
• Every new API (including internal ones) has full XML docs
• Code follows all style conventions

Other information

[aaronpowell]

@programmation I've kicked off a workflow run. Assuming it builds there will be preview NuGet packages available that you can download (or pull from the Azure DevOps feed) to test it out.

[programmation]

@dotnet-policy-service agree

[programmation]

Apologies if this isn't the correct way to fix a (tiny) problem in the original PR.

[aaronpowell]

I'll wait for @esskar to have a review as their the code owner of this integration

[esskar]

Looks good from the code side; thanks.

But edge labels/edge_id are no longer supported; there is no way to get an edge_id from ngrok anymore, instead you acquire a (free) custom domain from them - this was already supported by the integration.

[aaronpowell]

Looks good from the code side; thanks.

But edge labels/edge_id are no longer supported; there is no way to get an edge_id from ngrok anymore, instead you acquire a (free) custom domain from them - this was already supported by the integration.

What issue might someone see as a result of edge labels not being supported and using the integration?

[programmation]

The issue I had (and the reason for the PR) was that although I have a free URL, if I specify the URL in the Aspire config I get an error at ngrok, but if I omit it, ngrok creates a whole new randomised URL, which breaks my mobile test setup. I could not find any documentation at ngrok on how to upgrade from edge labels to whatever they're doing now so I reached out to them for clarification. In the meantime though I needed something to enable me to use the features that I've been using via docker-compose.