fix(bedrock-agentcore-alpha): use static construct ID for asset-based runtime artifacts

[alvazjor]

Issue # (if applicable)

Closes #35968

Reason for this change

Using AgentRuntimeArtifact.fromAsset() adds an MD5 hash of the directory path to the construct ID, causing CDK pipelines to self-mutate whenever the Docker image directory contents change. This is inconsistent with how other Docker images handle assets.

Description of changes

• Removed the md5hash import and usage from AssetImage.bind() and changed the construct ID from AgentRuntimeArtifact${hash} to a static AgentRuntimeArtifact
• Added unit tests to verify the static ID behavior
• Fixed existing test paths to use path.join(__dirname, ...) for portability

Describe any new or updated permissions being added

NA

Description of how you validated changes

Added unit tests

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Merge Queue Status

✅ The pull request has been merged

This pull request spent 30 minutes 7 seconds in the queue, including 29 minutes 58 seconds running CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(bedrock-agentcore-alpha): use static construct ID for asset-based runtime artifacts #36241
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(bedrock-agentcore-alpha): use static construct ID for asset-based runtime artifacts #36241
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.