Adds type summary to the generation pipeline

[zengin]

• Adds a Powershell script to generate a type summary
• Adds a pipeline step to add typeSummary.txt file at the root of the repo, so that we can watch the type changes in a cleaner format together with the code changes
• What that diff looks like can be found here: ffeeec4
  • check the typeSummary.txt file

[zengin]

Perf note: The script took 43 seconds to run on the V1 repo, which should be OK to have for the added benefit.

[MIchaelMainer]

This will really help on the messy metadata changes.

[MIchaelMainer]

Does GetParameters() return the parameters in the order that they are defined? I'd imagine it does but I want to check.

[zengin]

I have the same assumption given that Reflection is used in places where people can create Invoke methods by following the parameter order.

I couldn't find documentation confirming this, but a quick look revealed that I always get the same order from the definition. I also swapped orders in one of the methods, rebuilt the dll and the only diff was on that parameter order.

So I am fairly confident that this is a deterministic order and it will raise diffs if someone changes the order.