feat(synthetics): allow root level canary scripts files for Puppeteer versions 11 and greater

[nithinv13]

Issue # (if applicable)

Closes #.

Reason for this change

Support packaging structure changes for new runtimes based on NodeJS runtime Puppeteer framework

Description of changes

As part of the new Puppeteer based runtimes (syn-nodesj-puppeteer-11.0 and greater), users can have the canary script files in the root directory and are not required to use the nodejs/node_modules sub-directory to include the canary scripts. This PR ensures that we do not throw validation exception when users have their canary script in the root directory.

Current requirement for the folder structure for Puppeteer based runtimes
Canary/nodejs/node_modules/index.js

With the above changes, along with the above structure support, we also support
Canary/index.js

Describe any new or updated permissions being added

No new permission have been added

Description of how you validated changes

Validated the changes by creating a sample canary with the changes in place and ensured that we are able to create canaries on runtime version syn-nodejs-puppeteer-11.0 with the index.js files in the root directory as well as index.js file being present in the nodejs/node_modules subdirectory inside the root directory.

Added corresponding unit tests and integration 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.

[aemada-aws]

This is a feat not a chore. Please update the title, that will also require you to add integ tests and readme changes.

[aws-cdk-automation]

(This review is outdated)

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

[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]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[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).

[aemada-aws]

@Mergifyio update

[mergify]

update

❌ Mergify doesn't have permission to update

Details

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/integration-test-deployment.yml without workflows permission

[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]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35426 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: Required status check "validate-pr" is queued.).

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[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).

[aemada-aws]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[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.