Update rack-protection to 2.0.1

What does this MR do?

Updates rack-protection to 2.0.1.

Are there points in the code the reviewer needs to double check?

No.

Why was this MR needed?

To keep dependency gems up-to-date.

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• [n/a] Documentation created/updated
• [n/a] API support added
• [n/a] Tests added for this feature/bug
• Review
  • [n/a] Has been reviewed by UX
  • [n/a] Has been reviewed by Frontend
  • Has been reviewed by Backend
  • [n/a] Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• [n/a] Internationalization required/considered
• End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes #44388 (closed)