Ensure that the hub client proxy generator correctly processes both explicit and inferred generic type arguments

[MattyLeslie]

Fix HubClientProxyGenerator to Handle Inferred Generic Type Arguments

Issue:
The HubClientProxyGenerator was not generating proxy code for methods using inferred generic type arguments. This was because the initial syntax node filter only considered methods with explicit generic types.

Solution:
Updated the syntax node filter to include both explicit and inferred generic type arguments by changing the filter condition to SimpleNameSyntax. This ensures that all relevant methods are processed for proxy generation.

Fixes #43510

[BrennanConroy]

Could you please add test(s)?
https://github.com/dotnet/aspnetcore/blob/main/src/SignalR/clients/csharp/Client/test/UnitTests/HubClientProxyGeneratorTests.cs

[MattyLeslie]

Hey @BrennanConroy, I added tests to HubClientProxyGeneratorTests, however after opening HubClientProxyGeneratorTests & HubServerProxyGeneratorTests when building I get an error with GetHubServer as depicted in the screenshots, when switching to the main branch, I am still presented with the errors. I don't see anything I've changed to attribute this to. I've tried re-setting my local environment to no avail. I just wanted to reach out to you and ensure I'm not missing something. Any direction would be appreciated.

[BrennanConroy]

I think VS has some weird behavior with source generators being referenced via project reference. Sometimes building via the command line first might help. But the issue in the PR looks like you just need to make MyClient public or internal.