TSPS-404 Update to TCL 1.1.36 to get 401 response for Sam user not found

[mmorgantaylor]

Description

With this change, we now get back a 401 rather than a 500 from TCL/Sam when Sam doesn't recognize the user calling a Teaspoons API endpoint.

This supports a PR in the terralab repo: DataBiosphere/terra-scientific-pipelines-service-cli#42

{
  "message": "User not found",
  "statusCode": 401,
  "causes": []
}

Jira Ticket

https://broadworkbench.atlassian.net/browse/TSPS-404

Checklist (provide links to changes)

• Updated external documentation (if applicable)
• Updated internal documentation (if applicable)
• Planned non patch version bump (if applicable)
• Updated CLI PR: TSPS-404 Point new-to-Terra users to register with Terra terra-scientific-pipelines-service-cli#42

[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

[gbggrant]

Looks good to me (but I'm not sure how to verify the corrected behavior).

[jsotobroad]

is a 401 the only new code we shoudl be getting or also 403 or 404s?

[mmorgantaylor]

is a 401 the only new code we shoudl be getting or also 403 or 404s?

only 401. TCL receives the 403 from Sam and converts it to a 401.

[jsotobroad]

perfect, thank you!