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

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
  •