Provide a supported approach to import local (not dynamic) version of JS SDK as module

Nobody has claimed this yet.

There are several ways to initialize Aplication Insights and currently static loading when importing as module is not covered. We need to provide a supported way and update readme.

| | **Dynamic loading.** JS script tag is inserted in the head of the page. This is the recommended approach as our CDN is getting frequent updates. | **Static loading.** You are responsible for including JS script tag or bundling the script with your other scripts. |
| --- | --- | --- |
| **Using initialization `snippet`** | [Dynamic loading with snippet](README.md#use-js-snippet-and-initialize-dynamically-download-full-application-insights-script-from-cdn) This is default approach used in a new ASP.NET application created in Visual Studio. Use this for MVC applications. | [Host AI JS SDK and initialize statically](README.md#include-ai-js-sdk-script-and-initialize-statically). Cordova applications where you would like to embed scripts into your application for faster loading is an example of when you would use this approach. |
| **Using module import** | [Dynamic loading using module import](README.md#import-as-a-module-and-initialize-dynamically-download-full-application-insights-script-from-cdn). This is the recommended approach for modern modular applications. | **missing today** |

Start with the module-import and static-loading sections linked in README.md and compare their initialization guidance. Determine the supported local module-import approach, then update README.md with the missing path and an example. Done means the static module-import case is supported and documented alongside the existing dynamic and script-based options.

Written by the indexing model from the issue text.