typings: replace `custom-globals` with `static-types` in all projects if possible

[Hotell]

We introduced new global typings for declaring static assets in typings/static-assets. Prior to this change, static asset extensions were mixed with typings/custom-globals which defines additional ECMA definitions for IE11 and legacy browsers.

As vNext packages are no longer supporting legacy browsers we need to get rid of all custom-globals in those packages ( this will be automated via migrate-converged-pkg generator ).

Actual behavior:

All/most packages use custom-globals global types

Expected behavior:

All projects use global types as needed:

• vNext packages don't use those types at all
• apps / additional projects need to be evaluated and changed manually
• Once these 2 previous points are implemented we can get rid of hard dependency on static-assets within custom-globals
  • 

[varholak-peter]

• Are we providing a guide for apps/projects on how to change manually?
• Can we somehow track which projects have not yet migrated or what would be our strategy to ensure people updated it? (As I understand, this needs to happen in order for things to work properly.)

[msft-fluent-ui-bot]

Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes.

Still require assistance? Please, create a new issue with up-to date details.

[Hotell]

not implemented yet