fix(import): only set resourceName when executionRoleArn is present

[jesseturner21]

Summary

• Fixes e2e test failure on main where agentcore import gateway fails for gateways without a roleArn
• resourceName and executionRoleArn must co-vary per the schema refine added in feat: add gateway import command with executionRoleArn support #855. When a gateway has no roleArn, resourceName must also be omitted to pass validation
• Without this fix, toGatewaySpec always sets resourceName but conditionally sets executionRoleArn, causing the refine to reject the spec

Test plan

• Unit tests updated and passing (370/370)
• e2e tests pass on CI (gateway import without roleArn)

[github-actions]

Package Tarball

aws-agentcore-0.11.0.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-996-tarball/aws-agentcore-0.11.0.tgz

[agentcore-cli-automation]

Reviewed the change. The fix is correct and minimal — tying resourceName to the same gateway.roleArn predicate as executionRoleArn preserves the schema refine invariant (co-vary or both omitted), and the added unit tests cover both branches.

One minor semantic observation (not blocking): if a gateway ever does come back from GetGateway without a roleArn, the imported spec will now have neither resourceName nor executionRoleArn, so CDK will attempt to create a new gateway under a generated name rather than adopt the existing one. In practice real gateways always have a role, and the CloudFormation import step would fail loudly if this ever happened, so I don't think it needs to change here — just worth being aware of.

LGTM to merge.