Add security for keypair creation in configure_ec2 pattern

[GomathiselviS]

Refer : https://issues.redhat.com/browse/ACA-2059
This PR ensures that private keys to ec2 instances are not available in job logs by default

[mandar242]

Suggested change

	To enable SSH access to the EC2 instance from your local machine, you need to do 2 things:
	To enable SSH access to the EC2 instance from your local machine, following 2 actions are required:

[patchback]

Backport to stable-3: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply c7c6737 on top of patchback/backports/stable-3/c7c6737a2a2695198185a7e4450c58d60ea4def8/pr-129

Backporting merged PR #129 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/redhat-cop/cloud.aws_ops.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-3/c7c6737a2a2695198185a7e4450c58d60ea4def8/pr-129 upstream/stable-3

4. Now, cherry-pick PR Add security for keypair creation in configure_ec2 pattern #129 contents into that branch:

   $ git cherry-pick -x c7c6737a2a2695198185a7e4450c58d60ea4def8

   If it'll yell at you with something like fatal: Commit c7c6737a2a2695198185a7e4450c58d60ea4def8 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x c7c6737a2a2695198185a7e4450c58d60ea4def8

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Add security for keypair creation in configure_ec2 pattern #129 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-3/c7c6737a2a2695198185a7e4450c58d60ea4def8/pr-129

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-3: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-3/c7c6737a2a2695198185a7e4450c58d60ea4def8/pr-129

Backported as #145

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.