Use stubbed key and certificate in Helm factory

What does this MR do?

Every time we create a helm application record in tests we generate a certificate for it, which is very slow. This merge request uses a pre-generated certificate and key to avoid generating a new one every time.

On my local machine, this brings the runtime for all cluster application specs from ~350 seconds to ~130 seconds.

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry for user-facing changes, or community contribution. Check the link for other scenarios.
• [-] Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Performance and testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team