chore!: Python and Go codegen runs in polymorph_code_gen target

[lucasmcdonald3]

Issue #, if available:

Description of changes: Python and Go run as part of polymorph_code_gen.

Breaking change: The dependency-library-name CLI option has been removed. You must specify either/both of:

• python-dependency-module-name
• go-dependency-module-name

I have some downstream PRs open in Crypto Tools repos that use Python and/or Go codegen:

• chore(build): Bump smithy-dafny, update Python/Go Makefile variables aws/aws-cryptographic-material-providers-library#1292
• chore(build): Bump Smithy-Dafny, update Go Makefile variables aws/aws-encryption-sdk#752

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

[texastony]

@lucasmcdonald3 If you have the time, it would be great to also add Python to the clean recipe.
For example, right now, when ever I need to re-polymorph the MPL, I run:

gmake clean;
rm -rf runtimes/python/src/aws_cryptographic_material_providers/smithygenerated

It should be straightforward to add the rm -rf of the Python Smithy generated to the Makefile.

[lucasmcdonald3]

Putting this PR on ice until Go gets merged.

This would create hiccups for Go that, ideally, we'd avoid for now.

[ShubhamChaturvedi7]

Changes look good, but let's wait till we have Go fully merged and has CI, which should be this week.

[lucasmcdonald3]

Keeping this unmerged until Go ESDK is released.
The breaking change to the Makefile variables would cause a hiccup for Go, and we'd prefer to keep that moving at full speed.