Reorganize packages/

[eladb]

The current flat structure of our monorepo makes it hard to work with it as it's hard to scope down lerna operations only to certain parts of it. Eventually, once we start publishing to NPM, we will want to manage various module (or module groups) in separate repos, but for now, let's try to organize it in a way that will make it more practical to use.

Here's an initial proposal:

packages/framework
    aws-cdk
    aws-cdk-applet-js
    aws-cdk-assert
    aws-cdk-cloudformation-diff
    aws-cdk-custom-resources
    aws-cdk-cx-api
    aws-cdk-resources
    aws-cdk-toolkit
    aws-cdk-util
packages/awslibs
    aws-cdk-acm
    aws-cdk-cloudtrail
    aws-cdk-codebuild
    aws-cdk-codecommit
    aws-cdk-codepipeline
    aws-cdk-dynamodb
    aws-cdk-ec2
    aws-cdk-events
    aws-cdk-iam
    aws-cdk-kms
    aws-cdk-lambda
    aws-cdk-neptune
    aws-cdk-quickstarts
    aws-cdk-rds
    aws-cdk-route53
    aws-cdk-rtv
    aws-cdk-s3
    aws-cdk-sns
    aws-cdk-sqs
packages/build-tools
    cfn2ts
    pkglint
    pkgtools
    simple-resource-bundler
packages/bundles
    cdk-bundle-all
    cdk-bundle-docs
    cdk-bundle-java
packages/examples

[eladb]

We also need to take into account the fact that we are going to move all modules to the "@aws-cdk" scope. I wonder if this is orthogonal to the directory structure or lerna requires that scopes will be represented by the tree structure as well

[rix0rrr]

Don't really care for the name awslibs, agreed on all the rest.

I don't think the source directory structure has to mirror the scopes--the node_modules install path definitely will and that's all that's necessary for require() to work--but we might as well name the directory @aws-cdk/ anyway. It's nice and clear and avoids us having to think of a good name for the directory :P

[rix0rrr]

Turns out we did most of this and it seems to be fine for now. Closing.