Add missing global:: prefix to type inference method parameters

[jjonescz]

Fixes #7103.
Fixes #8316.

[jaredpar]

The original bug had the synthetic type name being generated being a user defined type name. Whenever I see that my brain says

Are we making sure that we don't re-introduce the global::dynamic and global::(int x, int y) bugs again?

All the tests here though are around a generated IEnumerable<T>. Is there a way for the user to control the type name generated here such that it's a user defined type? The samples in the bug seem to indicate such is possible.

[jjonescz]

All the tests here though are around a generated IEnumerable<T>

Those are only the existing tests. There's one new test with user-defined type global::MyApp.MyClass<T>.

Are we making sure that we don't re-introduce the global::dynamic and global::(int x, int y) bugs again?

Good question. Added a test demonstrating that tuples still work. (Dynamic probably cannot be verified here as this code path is only for generic types.)

[jjonescz]

@chsienki @dotnet/razor-compiler for the second review

[jjonescz]

@chsienki @dotnet/razor-compiler for a second review, please