Handle bad css_id when navigating to a judge assign queue

[hschallhorn]

As of #13433, when an invalid css_id is used in /queue/<css_id>/assign, the error is not handled.

Correct css_id

Bad css_id

// 20200420142400
// http://localhost:3000/queue/BVAAAAAAAABSHIRE/assign

{
  "errors": [
    {
      "status": 400,
      "title": "\"BVAAAAAAAABSHIRE\" is not a valid CSS_ID or user ID",
      "detail": "\"BVAAAAAAAABSHIRE\" is not a valid CSS_ID or user ID"
    }
  ]
}

This should instead redirect to our normal 404 page

AC

• When the user navigates to an assign queue that does not exist, we should redirect them to our 404 page

[ajspotts]

what is this chart?

1 | ||
2 | ||||||||||
3 | 
5 | 
8 | 

Why 1?

• Seems straightforward

Why 2?

• I dunno how!
• Assuming I can ask someone how this is done. (fail ActiveRecord::NotFound)

[yoomlam]

Should also check https://www.caseflowdemo.com/queue/appeals.
See https://dsva.slack.com/archives/CJL810329/p1587406296458100

[hschallhorn]

This is causing a sentry alert as well https://sentry.ds.va.gov/department-of-veterans-affairs/caseflow/issues/9927/

[yoomlam]

Using ActiveRecord::RecordNotFound shows this:

[yoomlam]

BEFORE	AFTER