docs: add backstage-cli usage guide for RHDH

[kadel]

Document how to use @backstage/cli auth and actions commands with RHDH, including auth plugin setup, OAuth2 endpoint configuration, standalone usage workaround for npm peer dependency conflicts, and troubleshooting.

Assisted-by: Claude Code

Description

Please explain the changes you made here.

Which issue(s) does this PR fix

related to https://redhat.atlassian.net/browse/RHIDP-14120

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.86%. Comparing base (105732d) to head (b8506ea).
⚠️ Report is 54 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4901      +/-   ##
==========================================
- Coverage   53.65%   52.86%   -0.80%     
==========================================
  Files         121      109      -12     
  Lines        2350     2132     -218     
  Branches      539      537       -2     
==========================================
- Hits         1261     1127     -134     
+ Misses       1084     1004      -80     
+ Partials        5        1       -4     

Flag	Coverage Δ
rhdh	52.86% <ø> (-0.80%)	⬇️

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 105732d...b8506ea. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

The container image build workflow finished with status: cancelled.

[github-actions]

The container image build workflow finished with status: cancelled.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Image was built and published successfully. It is available at:

• quay.io/rhdh-community/rhdh:pr-4901
• quay.io/rhdh-community/rhdh:pr-4901-b8506ea2

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.

[gabemontero]

@yangcao77 - what @kadel has here looks analogous to what I saw from your google doc https://docs.google.com/document/d/1X_kIDDhyTdndrK81bfJL9bvLm0z5ShJc42tHXg4RQ84/edit?tab=t.0 and
https://docs.google.com/document/d/1ZAfV6oTNnhcKg_xA5z0u6-t_5NMj_NYlvm5zZQgEWBk/edit?tab=t.0#heading=h.lwajsvbry7av and
https://docs.google.com/document/d/1wgH8yENCTzxml7rgbvKgixhw75VrsFJUzIFdNmKsQVg/edit?tab=t.0#heading=h.44w104d3ha07

I think you two have been corresponding on CLI work, but admittedly am not 100% certain of that

First blush, I would think we would want the state of the CLI (including perhaps those findings of things that need enhancement you've got) stored somewhere like this in github, no ? Perhaps some link to docs like this in the rhdh-plugins repo too ...

I did try to search through RHIDP-14120 (IIUC that lead to the producing of @yangcao77 's google docs) but saw no discussion around even considering storing this useful information in github somewhere (vs. just google docs) ...

apologies @kadel @yangcao77 if what I am asking about has been sorted out somewhere and I'm just missing it

thanks