Add v1 meeting RSVP mock data for board members

Added a new playbook step to create meeting RSVP (invite response) mock
data for board member registrants. This publishes RSVP events to the
lfx.index.v1_meeting_rsvp NATS subject for indexing in OpenSearch.

The RSVP data includes:
- Unique ID and registrant association
- Meeting and occurrence references
- User information (name, email, username, org, job title)
- Response status (accepted/declined/maybe) with random selection
- Scope set to "all" for applying to all meeting occurrences
- Response date, SES message ID, and email details
- Creation and modification timestamps

All fields match the inviteResponseInput Go struct schema to ensure
compatibility with the indexer service.

Generated with [Claude Code](https://claude.com/claude-code)

Signed-off-by: Andres Tobon <[email protected]>

Author: andrest50

playbooks/v1_meetings/umbrella_board_meeting/board_meeting.yaml

@@ -217,6 +217,50 @@ buf_board_meeting_committee_participants_access_update:
     {% endif %}
     {% endfor %}
 
+buf_board_meeting_committee_participants_rsvps_create:
+  type: nats-publish
+  params:
+    # Create the meeting registrant's RSVP in OpenSearch (via indexer).
+    subject: lfx.index.v1_meeting_rsvp
+  steps:
+    # Count matches the count in buf_board_members.
+    {% for i in range(board_member_count) %}
+    {% set rsvp_response_date = fake.date_time_between(start_date='-30d', end_date='now') %}
+    - json:
+        action: created
+        headers:
+          authorization: !jwt bearer=true,aud=lfx-v2-project-service,principal={{ fake.user_name() }},email={{ fake.email() }}
+          x-on-behalf-of: !jwt bearer=true,aud=lfx-v2-project-service,principal=clients@m2m_helper
+        data:
+          id: "{{ fake.uuid4() }}"
+          meeting_and_occurrence_id: ""
+          meeting_id: "{{ meeting_id }}"
+          occurrence_id: ""
+          registrant_id: !ref "buf_board_meeting_committee_participants_create.steps[{{ i }}].json.data.id"
+          email: !ref "buf_board_members.steps[{{ i }}].json.email"
+          name: !sub "${buf_board_members.steps[{{ i }}].json.first_name} ${buf_board_members.steps[{{ i }}].json.last_name}"
+          user_id: ""
+          {% if member_has_username[i] %}
+          username: {{ fake.user_name() }}
+          {% else %}
+          username: ""
+          {% endif %}
+          org: !ref "buf_board_members.steps[{{ i }}].json.organization.name"
+          {% if fake.pybool() %}
+          job_title: ""
+          {% else %}
+          job_title: "{{ fake.job() }}"
+          {% endif %}
+          response: "{{ fake.random_element(elements=('accepted', 'declined', 'maybe')) }}"
+          scope: "all" # There are three scopes: single, all, this_and_following. However, "all" is the easiest to support.
+          response_date: "{{ rsvp_response_date.isoformat() }}Z"
+          ses_message_id: "{{ fake.uuid4().replace('-', '')[0:40] }}"
+          email_subject: "Re: Invitation to Monthly Board Meeting"
+          email_text: "{{ fake.sentence() }}"
+          created_at: "{{ rsvp_response_date.isoformat() }}Z"
+          modified_at: "{{ rsvp_response_date.isoformat() }}Z"
+    {% endfor %}
+
 #
 # Loop over each past meeting.
 #