Update catalog.yaml

[mscavnicky]

Stakeholder Overview (learn more)

Risk Estimate (learn more)

[Replace this with a description of the risk, if any, and how the change will be deployed.]

• ⚠️ Big/complex change
• ⚠️ Big splash zone
• ⚠️ High stakes if errors occur
• ⚠️ Low confidence
• ⚠️ Not hidden by feature flag
• ✅ Negligible risk!

Changes

Updated Dependencies

• None

Ticket

Monday issue

Screenshots

Notes

Recommended reading: Code Review guide

Optional Tasks

• Include 🎩 Instructions
• Update the readme (README.md)
• Update the API or architecture docs (e.g. docs/api.md)

Library-Specific

• Increment the changelog (CHANGELOG.md)
• Increment the version number (lib/version.rb)
• Release & Tag the version above in Github

Performance

• Are there any new queries in your change set that might require new indexes?
• Do any new queries require time-boxing to avoid table-scans when the data grows?

Data & Analytics Dependencies

• For customer-facing applications, are there any GA tagging changes that are needed or created by this change? If so, have those been discussed with D&A?
• Has Data Engineering been notified of any schema changes?

What GIF Best Describes This Pull Request?