chore: Refactor to build into single artifact

[lavaleri]

Refactor contains the following major changes:

• Updated all namespaces to move under DynamoDbEncryption and updated Makefile to handle building multiple namespaces
• Moved local service containing the transforms to a new namespace dynamoDbEncryption.transforms
• Move the DynamoDbItemEncryptor to a new namespace dynamoDbEncryption.itemEncryptor.
• Created new empty DynamoDbEncryption local service
• Moved "common" structures such as AttributeActions and LegacyPolicy to DynamoDbEncryption service
• Updated custom Java tests to use TestNG
• remove polymorph submodule
• move Dafny ESDK submodule to submodules/MaterialProviders

Manual smithy change added:

• Had to update the DynamoDbEncryptionTransforms Types file because it was not importing it's config file correctly.

Manual smithy changes preserved:

• DynamoDbItemEncryptor Types still manually defines some Modifies ensures, as otherwise our resource count is exceeded.
• DynamoDbEncryption ToNative still manually updated to make the LegacyEncryptor work correctly.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[seebees]

Small comment otherwise looks pretty good

[seebees]

Should we have this include the root one and then modify it accordingly?

[lavaleri]

We could, but just duplicating it here was easier. I would prefer to backfill the one in MPL to match the one here.

Realistically, it's only for convenience/to avoid duplication that the SharedMakefile belongs to MPL. The way I think of this is a bit similar to gradle, where each smithy-dafny project would come with some canonical SharedMakefile that gives you most of the goodness you are already looking for. And this "SharedMakefile" exists in multiple places just because each project needs access to it, and shoudn't have to dig into it's dependencies to do so.

[seebees]

Is this a new target because you need to break it up?

[lavaleri]

Yes, otherwise it takes >30min for CI to turn green. I figure once we launch and aren't doing as much development on it, we could switch back to the single target to be extra sure we aren't missing any files.