fix(integ): remove CapacityProviderName exceeding 64-char limit

[vicheey]

Issue #, if available

N/A

Description of changes

Removed CapacityProviderName: !Sub "${AWS::StackName}-cp" from integration test templates function_lmi_custom.yaml and function_lmi_default.yaml. The resolved name exceeded the 64-character limit enforced by Lambda's CapacityProvider API, causing deployment failures (e.g. SamTranslatorLambda-sam-integ-stack-function-lmi-custom-eplzcyobezoy-cp is 72 chars). Since CapacityProviderName is optional, CloudFormation will auto-generate a valid name.

Description of how you validated changes

• Confirmed no integration test assertions depend on the CapacityProviderName value — the tests only use it as a lookup key via get_physical_id_by_logical_id, which works with auto-generated names.
• Verified both templates are syntactically valid after the change.

Checklist

• Review the generative AI contribution guidelines
• Adheres to the development guidelines
• Add/update transform tests
  • N/A — no transform logic changed
• Add/update integration tests
  • Updated existing integration test templates to remove the problematic property

Examples?

N/A

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.