[Feature]: Decouple makefile wrappers of dcap collateral phases

[butler54]

Feature Description

There are 5 distinct tasks

1. Platform collateral collection. This is cluster independent. Must happen every 30 days
2. Loading platform collateral via load-secrets (already covered)
3. Collecting from QGS id's
4. Registering the platform and generating pck certs (long lifespan)
5. Loading the pck certs into secrets.

today this seems to be awkwardly bundled up. (1/2) should be split off. 3-5 should either be run as one connected phase (e.g. bastion is connected, cluster is not) or discrete individual phases (e.g. collected QGS ids', take low side, register platform and download pck certs, take high sdie, load in).

Why Is This Needed?

Completely awkward to configure today if it's a disconnected bastion

Suggested Solutions

• Rewrite scripts in the make file.
• Be careful of the pck registristration process so far I had to actually pass keys by hand. The backend trying to use the keyring is problematic. Design if possible to pass the PCCS api key via envvar. this may need upstream code analysis

Proposed Acceptance criteria

• User can run each discrete phase serially with minimal issues.
• Should have necessary tooling to make sure the PCK client tools https://github.com/intel/confidential-computing.tee.dcap/blob/main/tools/PcsClientTool are available as well (via git clone).