Improve parameter type naming for generic types

[olegKoshmeliuk]

🤔 What's changed?

Changed RuntimeBindingType.FullName behavior for generic types.
Before it was simple Type.FullName which is not working good for generic and nullable types.
Now it's using custom logic to provide better value for autocomplete for generic types.

Example new placeholders:

⚡️ What's your motivation?

Current behavior :

• List<string> => System.Collections.Generic.List`1[[System.String, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]
• int? => System.Nullable`1[[System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]

That is resulting bad autocomplete hints in VS Plugin. (it's using FullName as a Placeholder)
This PR will change autocomplete steps in VS to be more readable.
From placeholder: [0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]]
To placeholder: [List<String>]

🏷️ What kind of change is this?

• 🐛 Bug fix (non-breaking change which fixes a defect)

♻️ Anything particular you want feedback on?

📋 Checklist:

• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• Users should know about my change
  • I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.

---

This text was originally taken from the template of the Cucumber project, then edited by hand. You can modify the template here.

[olegKoshmeliuk]

@gasparnagy I open for suggestions.
I didn't add tests because I did't find good place.
Based on your suggestions I can create TestClass or Theory test for FullName getter.

[gasparnagy]

@olegKoshmeliuk Thx. Did you check if the VS extension code uses this for anything else than displaying it? Aren't we breaking any backwards compatibility?

[olegKoshmeliuk]

Possible breaking this code for generic types: BindingReflectionExtensions.cs#L15C9-L38C10 because it's comparing with Type.FullName

From what I saw VS extension expects <Namespace>.<Type> format in FullName like in non generic types. example so it's mostly a bug fix for VS extension
I tested locally autocomplete and binding discovery was working fine.

[gasparnagy]

Thx!