Changing the PATH order we set for using the cfnbootstrap script we have installed in virtualenv rather than using default scripts

[himani2411]

Description of changes

Changing the PATH order we set for using the cfnbootstrap script we have installed in virtualenv rather than using default scripts

• Adding Kitchen test

Tests

Locally

./kitchen.ec2.sh environment-install test cfn-bootstrap -c 7

release-3.9 -> #2730

References

• Link to impacted open issues.
• Link to related PRs in other packages (i.e. cookbook, node).
• Link to documentation useful to understand the changes.

Checklist

• Make sure you are pointing to the right branch.
• If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
• Check all commits' messages are clear, describing what and why vs how.
• Make sure to have added unit tests or integration tests to cover the new/modified code.
• Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

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

[enrico-usai]

Let's start merging this patch that is using the existing approach but will fix the issue.

Then we can improve this code, as suggested by @nyetsche in this issue: aws/aws-parallelcluster#5390

we could:

• do a source profile.sh in the user_data.sh, to have it loaded for that specific command.
• use #{cfn_bootstrap_virtualenv_path} in all other places in the code where we're calling cfn-something

In this way the cfn commands will be correctly loaded by our scripts but without impacting the PATH for all the users.