chore: namespace all private packages (aws#16689)

In order to remove any risk of supply-chain attacks leveraging naming
collisions with any of our private-only packages, move all of them into
the `@aws-cdk/` namespace, so that no third party can possibly seize one
of these names.

Also, normalized the order of dependencies in `package.json` files so
they are consistently alphanumerically ordered.

Author: RomainMuller

.github/workflows/pr-linter.yml

@@ -24,10 +24,10 @@ jobs:
         uses: actions/checkout@v2
 
       - name: Install & Build prlint
-        run: cd tools/prlint && yarn install --frozen-lockfile && yarn build+test
+        run: cd tools/@aws-cdk/prlint && yarn install --frozen-lockfile && yarn build+test
 
       - name: Validate
-        uses: ./tools/prlint
+        uses: ./tools/@aws-cdk/prlint
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           REPO_ROOT: ${{ github.workspace }}

CONTRIBUTING.md

@@ -602,7 +602,7 @@ The following linters are used:
 
 #### eslint
 
-All packages in the repo use a standard base configuration found at [eslintrc.js](tools/cdk-build-tools/config/eslintrc.js).
+All packages in the repo use a standard base configuration found at [eslintrc.js](tools/@aws-cdk/cdk-build-tools/config/eslintrc.js).
 This can be customized for any package by modifying the `.eslintrc` file found at its root.
 
 If you're using the VS Code and would like to see eslint violations on it, install the [eslint
@@ -780,7 +780,7 @@ the feature flag.
 A couple of [jest helper methods] are available for use with unit tests. These help run unit tests that test
 behaviour when flags are enabled or disabled in the two major versions.
 
-[jest helper methods]: https://github.com/aws/aws-cdk/blob/master/tools/cdk-build-tools/lib/feature-flag.ts
+[jest helper methods]: https://github.com/aws/aws-cdk/blob/master/tools/@aws-cdk/cdk-build-tools/lib/feature-flag.ts
 
 ## Versioning and Release