refactor: use 'extension' for file names (#4969)

To keep things unified, the entrypoint files for
the extension should use the 'extension' terminology
instead of 'main'.

Signed-off-by: Nikolas Komonen <[email protected]>

Author: nkomonen-amazon

packages/toolkit/package.json

@@ -48,8 +48,8 @@
         "onFileSystem:s3",
         "onFileSystem:s3-readonly"
     ],
-    "main": "./dist/src/main",
-    "browser": "./dist/src/mainWeb",
+    "main": "./dist/src/extension",
+    "browser": "./dist/src/extensionWeb",
     "engines": "This field will be autopopulated from the core module during debugging and packaging.",
     "contributes": "This field will be autopopulated from the core module during debugging and packaging.",
     "scripts": {

packages/toolkit/src/main.ts renamed to packages/toolkit/src/extension.ts

@@ -13,14 +13,14 @@ module.exports = (env, argv) => {
     const config = {
         ...baseConfigFactory(env, argv),
         entry: {
-            'src/main': './src/main.ts',
+            'src/extension': './src/extension.ts',
         },
     }
 
     const webConfig = {
         ...baseWebConfigsFactory(env, argv),
         entry: {
-            'src/mainWeb': './src/mainWeb.ts',
+            'src/extensionWeb': './src/extensionWeb.ts',
         },
     }