Update VS Code launch.json to use net9.0

[gldraphael]

Description

This PR fixes the VS Code launch tasks, to make it easier to launch projects from VS Code from within a dev container.

Related issues

n/a

Testing

This PR was tested by running the launch tasks.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Skip (This change is for dev environments)

[brendankowitz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mikaelweave]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[gldraphael]

Thank you for the review, @mikaelweave. I have some time on my hands and would love to help with a few issues over the next couple weeks. It would be a great way for me to learn more about FHIR.

Should I just pick one of the "Up for grabs" issues?

[LTA-Thinking]

Hi @gldraphael
I don't know if you still have time or interest, but yes feel free to pick up any up for grabs issue. I'm afraid we don't have much bandwidth to help bring people up to speed, but if you have any questions feel free to ask in the associated issue or in a PR.

[gldraphael]

Thanks @LTA-Thinking, I will do so as and when I get the time...