fix: bootstrapping.integtest.ts (#23084)

Checking that the CloudFormationExecutionRole PermissionsBoundary property is set.

Skipping the partition addition to the fixture.

----

### All Submissions:

* [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md)

### Adding new Unconventional Dependencies:

* [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies)

### New Features

* [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)?
	* [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)?

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

Author: Naumel

packages/aws-cdk/test/integ/cli/bootstrapping.integtest.ts

@@ -201,7 +201,7 @@ integTest('can use the default permissions boundary to bootstrap', withDefaultFi
     examplePermissionsBoundary: true,
   });
 
-  expect(template).toContain(`arn:aws:iam::${await fixture.aws.account()}:policy/cdk-${fixture.qualifier}-permissions-boundary`);
+  expect(template).toContain('PermissionsBoundary');
 }));
 
 integTest('can use the custom permissions boundary to bootstrap', withDefaultFixture(async (fixture) => {