[security] Move SPIRE Server Into its Own Namespace

[v0lkan]

Move SPIRE Server to Its Own Namespace

Description

This PR moves SPIRE server into its own namespace for better isolation and security.

There are additional changes too that I’ll annotate in the code review comments.

Changes

• Moved SPIRE Server to spire-server namespace (from spire-system; configurable).
• Configuration changes that allow this.
• Added OpenShift-related values to ignoreNamespaces.
• Other minor changes.

Test Policy Compliance

• [x] I have added or updated unit tests for my changes.
• [x] I have included integration tests where applicable.
• [x] All new and existing tests pass successfully.

Code Quality

• [x] I have followed the coding standards for this project.
• [x] I have performed a self-review of my code.
• [x] My code is well-commented, particularly in areas that may be difficult to understand.

Documentation

• [x] I have made corresponding changes to the documentation (if applicable).
• [x] I have updated any relevant READMEs or wiki pages.

Additional Comments

Include any additional comments or context about the PR here.

Checklist

Before you submit this PR, please make sure:

• [x] You have read the contributing guidelines and especially the test policy.
• [x] You have thoroughly tested your changes.
• [x] You have followed all the contributing guidelines for this project.
• [x] You understand and agree that your contributions will be publicly available under the project's license.

By submitting this pull request, you confirm that my contribution is made under the terms of the project's license and that you have the authority to grant these rights.

---

Thank you for your contribution to VMware Secrets Manager 🐢⚡️!

[v0lkan]

@BulldromeQ » This aligns better with RIC OpenShift deployment, where SPIRE Server is in its own namespace.

And it is better security regardless.