Upgrade BlazorWasmDebugging to 1.1.3

[Nick-Stanton]

It's been a while since we've published a new version (currently 1.1.0 is the most recent). Incrementing the version because of the addition of #7929, then will walk through publishing on resolution of this PR.

My understanding of the publishing process is from the guide written by @captainsafia here. Please correct me if this process is no longer correct.

[TanayParikh]

Should we consider aligning this with the O# versioning?

[mkArtakMSFT]

@dotnet/razor-tooling can this be merged or are there any specific processes we should follow?

[davidwengier]

@TanayParikh I think you merged the last one of these PRs. Do you still have permission? Otherwise I can do it, but I have no context here. I assume good faith and everything is correct :)

@allisonchou do you know how this is shipped?

[Nick-Stanton]

@davidwengier we have the right permissions, just wanted to make sure we weren't circumventing any process by merging before the tagged code owners saw it.

Do you think we should change this to reflect that or would you prefer that razor-tooling is still tagged on PRs here as an FYI?

razor/.github/CODEOWNERS

Line 10 in b42d501

/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension/ @dotnet/razor-tooling @captainsafia

As far as publishing goes, this is how I understand it. I figured the repo name is outdated but assumed the rest to be okay.

razor/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension/README.dev.md

Lines 25 to 30 in b42d501

	1. Generate a personal access token per the instructions in [the VS Code publishing guide](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=preview-page).
	2. Store the token from #1 in the `VSCODE_MARKETPLACE_TOKEN` environment variable.
	3. Increment the `patch` version of the package in the `package.json` file.
	4. Open a PR to the razor-tooling repo.
	5. Download the VSIX asset from the artifiacts of the build.
	6. Publish the VSIX asset using `vsix publish --packagePath ${pathFrom5} -p $VSCODE_MARKETPLACE_TOKEN`.

[davidwengier]

No issue from me merging this, and updating code owners as appropriate. @phil-allen-msft do you have any thoughts?

[phil-allen-msft]

The change seems very reasonable; let's make sure how to discuss testing before release.

[phil-allen-msft]

I think having razor-tooling aware that a new publish occurs is appropriate; we may end up seeing logged issues related to BlazorWasm debugging and knowing that 'something' has changed in the BlazorWasm debugging space in particular will help us to route the issues more correctly. I think it should mainly be a quick approve in the future, and I'd rather have natural processes handle it than require people to know/remember to send notice. For now, let's leave the codeowners unchanged.