feat: Add UTM parameter as an additional filter option

[zakacat]

What does this PR do?

Firstly, we understand that this issue was marked as "needs approval", but we decided to go ahead with the feature as we needed the material for our course. We understand that this PR may not ultimately be approved by a reviewer.

We began by extending the input filter schema to declare the five new UTM fields (utmSource, utmMedium, utmCampaign, utmTerm, utmContent), then modified the query handler to apply the corresponding WHERE clauses when those filters are active. From there we updated the booking filters hook to read the new filter values from the DataTable, registered the new columns in useBookingListColumns.tsx, and added the filterable column definitions to filterColumns.ts. The BookingListContainer.tsx was updated to map the new filter values through to the tRPC query input, and the English translation strings were added to common.json for the filter labels. Finally, we wrote unit tests to validate the new behaviour before and after the changes.

• Fixes Add UTM parameter as an additional filter option #28093 (GitHub issue number)
• Fixes CAL-7249 (Linear issue number - should be visible at the bottom of the GitHub issue description)

Image Demo:

BEFORE

AFTER

Mandatory Tasks (DO NOT REMOVE)

• [ X ] I have self-reviewed the code (A decent size PR without self-review might be rejected).
• [ X ] I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox. ---N/A---
• [ X ] I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

Units tests were added to apps/web/modules/bookings/hooks/useActiveFiltersValidator.test.ts and packages/trpc/server/routers/viewer/bookings/get.handler.test.ts, accordingly.

Run

yarn test get.handler.test apps/web/modules/bookings/hooks/useActiveFiltersValidator.test

to run tests specifc to the filters.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Add UTM parameter as an additional filter option ". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[cubic-dev-ai]

No issues found across 10 files