update rubysaml

[JPrevost]

This resolves an error we were seeing in staging. It is unclear why the problem only started showing up on staging when we added a different dependency, but it seems to so 🤷🏻

Developer

• All new ENV is documented in README
• All new ENV has been added to Heroku Pipeline, Staging and Prod
• ANDI or Wave has been run in accordance to
  our guide and
  all issues introduced by these changes have been resolved or opened as new
  issues (link to those issues in the Pull Request details above)
• Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

• The commit message is clear and follows our guidelines
  (not just this pull request message)
• There are appropriate tests covering any new functionality
• The documentation has been updated or is unnecessary
• The changes have been verified
• New dependencies are appropriate or there were no changes

Requires database migrations?

NO

Includes new or updated dependencies?

YES

[coveralls]

Coverage remained the same at 97.044% when pulling 4f9307f on update_rubysaml into 6b967b4 on main.