Add pull secret information to debug build issues

[StrongMonkey]

Checklist

• [x] The title of this PR would make a good line in Acorn's Release Note's Changelog
• [x] The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
• [x] All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
• [x] Commits follow contributing guidance
• [x] Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
• [x] Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
• [x] PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)

We used to see a lot of build issue regarding to push ECR registry with 403 errors, it turns out that it is extremely hard to troubleshoot ECR registry issue today. This PR prints out the pull secret it will pull out to push images to registry, so that we know which secret is pulled and used to push images and it will be easy to figure out which is going wrong.

It should only print out name and namespace so nothing sensetive will be printed out.