Ignore 401/403 errors when requesting queues

[jmthomas]

I ran through the entire sequence in 7.2.1 and could not reproduce any error message when visiting Command Sender. @ryanmelt please update the issue with reproduction steps.

closes #3452

Created new role inst-only. Created new user insty with new realm role ALLSCOPES__inst-only. Logged in and observed user could not send INST2 command:

Refreshing page shows no errors. Can send INST ABORT command:

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.83%. Comparing base (63a7272) to head (ade8667).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3598      +/-   ##
==========================================
- Coverage   79.84%   79.83%   -0.02%     
==========================================
  Files         694      694              
  Lines       58309    58309              
  Branches      728      728              
==========================================
- Hits        46556    46549       -7     
- Misses      11675    11682       +7     
  Partials       78       78              

Flag	Coverage Δ
python	81.22% <ø> (ø)
ruby-api	81.10% <ø> (-0.15%)	⬇️
ruby-backend	83.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ryanmelt]

If the user has cmd_info only for one target, they will get a 403 error.