feat(type-safe-api): support configuring custom gateway responses (#923)

Fixes #922

fix(static-website): fix deep linking access denied issue and bucket …

…deployment oom kill issue (#921)

CloudFront with S3 OAC returns a 403 instead of a 404 when an object is missing from an S3 bucket,
and so the redirect for single-page apps was broken. Updated to handle both 403 and 404 to be safe.
Additionally bumped the default memory size for the bucket deployment lambda which was being killed
due to exceeding the memory limit for just the default website.

Fixes #915, Fixes #909

feat(Pipeline): support usage of CodeConnections as Source step for P…

…DK Pipeline (#920)

* feat: support code connection and remove license build step

Added modifications to support code connection.
Removed one build step for licenses due to stack trace issues.

* fix: dependecy

fix depedndency

* fix: dependencies

why am I so dependant

* fixes

* removed commands

* removed commands

* feat: fixed latest - adding codestar

* chore: fix the merge conflits

* chore: remove extra folder

* chore: revert changes

* chore: keep the PDKPipeline same as previous

* chore: remove the validation

* chore: add test cases

* chore: rename the construct name to be consistent

* chore: update test snapshot

---------

Co-authored-by: Lucas <kaufluca@amazon.com>
Co-authored-by: EC2 Default User <ec2-user@ip-172-31-33-73.ap-southeast-1.compute.internal>

fix(type-safe-api): fix prepare-spec serialisation with tokens (#919)

CloudFormation has a bug where all primitive custom resource properties are converted to strings:
aws-cloudformation/cloudformation-coverage-roadmap#1037 . We previously
worked around this by serialising and deserialising using JSON.stringify to ensure these primitives
were resolved, however the use of tokens (for example an SSM parameter value for a response
template) caused an issue since the JSON.stringify is done at synth time before tokens have been
resolved, meaning that at deploy time the substituted values from CloudFormation aren't properly
escaped in the JSON and cause JSON.parse to fail in the custom resource. We revert the serialisation
change to instead coerce the specific primitive properties back to their original types in the
custom resource.

Fixes #918

fix(metrics): fix metric tag key (#916)

The correct key is 'tag' not 'tags'

feat: record usage metrics via cloudformation stack description (#912)

This change adds some information to the cloudformation stack descriptions
in order to help us record PDK usage. No network calls are added, this
simply utilises AWS's existing usage metrics and identifies PDK using our
unique id.

fix(type-safe-api): ensure api key auth can be disabled for specific …

…operations (#911)

A bug in cloudformation custom resources meant that api key authentication could not be disabled for
individual operations, as the boolean value `false` would be translated into the string `"false"` in
the cloudformation custom resource properties. Since `"false"` is truthy, the security scheme for
api key auth would be added to the operation where it should be disabled.

Fixes #910

fix(type-safe-api): fix reversed pydantic minimum and maximum (#908)

Correct the generated Pydantic fields so that `minimum` is greater than and `maximum` is less than.

fix #907

feat(type-safe-api): handlers default to python 3.13 and node 22 (#900)

* feat(type-safe-api): handlers default to python 3.13 and node 22

In order to default to the most secure configuration, handler functions now default to the latest
supported AWS Lambda runtimes for Python and Node.

BREAKING CHANGE: API handlers that don't specify the runtime version need to be validated with
Python 3.13 or Node 22.

* chore(type-safe-api): update test snapshots

Updating test snapshots in a separate commit for review readability.

---------

Co-authored-by: Jack Stevenson <jacsteve@amazon.com>

fix(type-safe-api): stop calling to_dict on lists in python runtime (#…

…905)

The template wasn't handling models with arrays of primitives properly, and it was getting handled
by the last else if statement for non-primitives. This change excludes arrays from the case.

fix #904