Description of problem:
When using the opc results config command to set configuration, the config does not persist across namespace switches. As a result, users encounter the following error when running results commands after switching namespaces:

Error: client error: 404 page not found (code: 404) 

 
The error message is misleading and does not indicate that the config is missing or needs to be re-set. This causes confusion and breaks the expected continuity of the CLI experience.

Workaround:
Re-run opc results config for each namespace after switching to set the config again manually.

Prerequisites (if any, like setup, operators/versions):

• opc results CLI with 1.19 operator

Steps to Reproduce:

Set opc results config & Run opc results config in Namespace A
Successfully run a results command (e.g., opc results pipelineruns list) in Namespace A
Switch to Namespace B using oc project <namespace-b>
Run the same opc results command in Namespace B

Actual results:

• Error message appears:

$ opc results tr list -n test
Error: client error: 404 page not found
 (code: 404)

• No indication that config must be reset.

Expected results:

• Config should ideally persist globally or have namespace-scoped awareness.

• If not, the error should be clear and suggest re-running opc results config explicitly.

Reproducibility:
Always

Acceptance criteria:

• opc results config supports multi-namespace or global persistence,
  OR

• CLI provides a meaningful error suggesting that config must be re-set for the new namespace.

Definition of Done:

• Fix implemented or documented.

• Error message updated (if persistence is not feasible).

• Tests added/updated.

• Documentation updated accordingly.

Build Details:

Additional info (Such as Logs, Screenshots, etc)