Fixes that Blazor focus extension could not focus SVG elements

[KristofferStrube]

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

PR Title
Fixes that Blazor focus extension could not focus SVG elements

PR Description
I have added an extra case in the typescript wrapper for the focus extension that checks if the parsed element is an SVG element and also if it has a tabindex.
I have added a simple test that covers this behaviour.

Fixes #35046

[dnfadmin]

All CLA requirements met.

[MackinnonBuck]

Looks great! 😃 Just a small wording suggestion.

[KristofferStrube]

Many thanks for the help @MackinnonBuck
I'm new to this so also had to learn when to pull upstream and when not to.

[KristofferStrube]

I was also a bit unsure if I had to commit the files in
https://github.com/KristofferStrube/aspnetcore/tree/main/src/Components/Web.JS/dist/Release
that are generated when building so I did not.

[MackinnonBuck]

@KristofferStrube You've done a great job identifying the necessary changes 🙂

I was also a bit unsure if I had to commit the files in
https://github.com/KristofferStrube/aspnetcore/tree/main/src/Components/Web.JS/dist/Release
that are generated when building so I did not.

Yes, we usually do commit those files. CI might fail if you don't. Would you be able to do so?

[KristofferStrube]

Yes, we usually do commit those files. CI might fail if you don't. Would you be able to do so?

Yep, I will get right on it but will have to build again locally first.

[KristofferStrube]

Hey @MackinnonBuck some of the tests failed due to what I think was a timeout or unlucky disc access errors. Can the CI tasks that failed be retriggered somehow or should I do something to fix this?