fix: call TokenRequest API when service account token secret is missing

[OchiengEd]

Description of the change:

This pull requests introduces code that will attempt to request a service account token via the TokenRequest API whenever an error is return regarding a missing service account token secret.

Motivation for the change:

Beyond Kubernetes 1.22, the service account token secret is not automatically created. Therefore, unless manually created, the service account token secret is expect to be missing.

As a result, it is necessary to update the Operator Lifecycle manager(OLM) code to account for the above change in the Kubernetes behavior.

Architectural changes:

Testing remarks:

Reviewer Checklist

• [ ] Implementation matches the proposed design, or proposal is updated to match implementation
• [ ] Sufficient unit test coverage
• [ ] Sufficient end-to-end test coverage
• [ ] Bug fixes are accompanied by regression test(s)
• [ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• [ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• [ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• [ ] Docs updated or added to /doc
• [ ] Commit messages sensible and descriptive
• [ ] Tests marked as [FLAKE] are truly flaky and have an issue
• [ ] Code is properly formatted

Closes #3376