Fix bad xrefs

[gewarren]

Suggest ignoring whitespace changes in the diff. The build is clean for these files so the xrefs are good.

Changes:

• remove extraneous preceding characters, for example [\], Type\[\], Type\[\], Type\[\]\[\], Type\[\]\<xref:System.Reflection.Emit.TypeBuilder.DefinePInvokeMethod%2A>
• replace %28 with (, %29 with ), %2C with , (and a few others to make xrefs more readable)

Contributes to dotnet/docs#19387.
@mairaw Thanks for letting me know about these!

[mairaw]

No problem! I know some of these links were not being reported on the build report but I don't see any drops on the number of warnings. Is that expected for this particular PR @gewarren?

[gewarren]

This just seemed to point to itself, so I deleted it.

[BillWagner]

This LGTM @gewarren

You can when ready.

[gewarren]

No problem! I know some of these links were not being reported on the build report but I don't see any drops on the number of warnings. Is that expected for this particular PR @gewarren?

Yes, the "xref links" weren't previously rendering as links when they were in the form [\], Type\[\], Type\[\], Type\[\]\[\], Type\[\]\<xref:System.Reflection.Emit.TypeBuilder.DefinePInvokeMethod%2A>. So they didn't generate any warnings. Now that they are links, they didn't introduce any new warnings either.

[gewarren]

Thanks for the reviews Maira and Bill!