[Client bug]: No way to accept microsoft.graph.calendarSharingMessage

Describe the bug
The client doesn't generate the code for the following URL

POST https://graph.microsoft.com/v1.0/me/messages/{message_id}/microsoft.graph.calendarSharingMessage/microsoft.graph.accept

To Reproduce
Accept method is missing

await graphClient.Me.Messages["{calendar_sharing_message_id}"].GraphCalendarSharingMessage.Accept.PostAsync()

or

await graphClient.Me.Messages["{calendar_sharing_message_id}"].Accept.PostAsync()

Expected behavior

await graphClient.Me.Messages["{calendar_sharing_message_id}"].GraphCalendarSharingMessage.Accept.PostAsync()

Screenshots
If applicable, add screenshots to help explain your problem.

Client version
v5.*

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Check the metadata

  <EntityType Name="calendarSharingMessage" BaseType="graph.message">
    <Property Name="canAccept" Type="Edm.Boolean" />
    <Property Name="sharingMessageAction" Type="graph.calendarSharingMessageAction" />
    <Property Name="sharingMessageActions" Type="Collection(graph.calendarSharingMessageAction)" />
    <Property Name="suggestedCalendarName" Type="Edm.String" />
  </EntityType>

  <Action Name="accept" IsBound="true">
    <Parameter Name="bindingParameter" Type="graph.calendarSharingMessage" />
    <ReturnType Type="graph.calendar" Nullable="false" />
  </Action>

Start by inspecting the Microsoft Graph metadata for calendarSharingMessage and its bound accept action, then trace how that metadata becomes the generated C# client surface. The work is done when the v5 client exposes GraphCalendarSharingMessage.Accept.PostAsync() for the documented endpoint and the corresponding generated behavior is covered by the project's existing checks.