feat: include tickets in RegistrationResource

[jennifer-richards]

This allows filtering meeting registrations by registration type via the v1 API. Includes the ticket data in the registration response - this is verbose, but avoids having to do lots of additional lookups to fetch data. This is not hard to make terser, but I don't think the quantity of data will be prohibitively large.

@evyncke

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.57%. Comparing base (c0115c9) to head (c4406b8).
⚠️ Report is 22 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #10223   +/-   ##
=======================================
  Coverage   88.57%   88.57%           
=======================================
  Files         317      317           
  Lines       42544    42546    +2     
=======================================
+ Hits        37682    37685    +3     
+ Misses       4862     4861    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[evyncke]

Thank you both

[evyncke]

And in case you wonder why I need this data, it is to build leadership, chairs, and authors expected attendance at the next IETF meeting. It was built in the COVID years so I still need to remove the COVID part in https://ehealth.vyncke.org/ietf/

Currently using a join/match (datatracker roles and registrations) based on full name but this quite error prone as opposed to datatracker ID.

[rjsparks]

As being discussed on tools-discuss, this should feed from a purposed API about meeting registration rather than API/v1, but also, as this is important to the IESG, shouldn't it be built into the datatracker?

[evyncke]

As being discussed on tools-discuss, this should feed from a purposed API about meeting registration rather than API/v1, but also, as this is important to the IESG, shouldn't it be built into the datatracker?

About the completely new API, my concern is that this would take a long time.

About getting it in the datatracker (guessing that you mean something similar to my quick & dirty PHP/JS page and backend PY scripts), why not ? But, to be honest this would be useful mainly to check attendance in meetings where there is some concerns about onsite participations, i.e., rather an exception. But, I had also this idea in mind to be honest