absentify: Update to v2 webhook payload format

[marc-on-github]

---

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

---

Summary

This PR updates the absentify connector to version 2.0 with improved webhook payload format and better descriptions.

Breaking Change Notice

This update introduces a new webhook payload format (v2). The connector now sends payload_version: "v2" when registering webhooks.

Backward Compatibility

• Existing flows will continue to work - they were registered without payload_version and will receive the v1 payload format
• New flows will use v2 format - the connector now sends payload_version: "v2" which triggers the new payload structure

Payload Format Changes

v1 (existing flows):

{
  "id": "...",
  "start": "2025-01-15",
  "details": {
    "status": "APPROVED",
    "requester_member": { ... }
  }
}

v2 (new flows):

{
  "event_type": "request_created",
  "body": {
    "id": "...",
    "start": "2025-01-15",
    "status": "APPROVED",
    "requester_member": { ... }
  }
}

Changes

• Updated to v2 webhook payload format with event_type and body wrapper
• Added payload_version parameter to webhook registration (internal, auto-set to "v2")
• Enhanced connector description for better discoverability in the Power Platform
• Improved trigger summaries: Changed from generic "Request created" to user-friendly "When a leave request is created"
• Added detailed operation descriptions with use-case examples
• Fixed security definition naming: Renamed from undefined to oauth2_auth
• Added x-ms-visibility: important for triggers to ensure proper visibility
• Added proper response codes (200, 201) for webhook subscriptions
• Fixed validation issues:
  • Added consumes/produces with application/json
  • Made body parameter required: true for webhook operations
• Updated brand color to #6465a7
• Added comprehensive response schemas for v2 payload

Validation

✅ Successfully validated with paconn validate command

[vmanoharas]

Hi @marc-on-github,

Please confirm that the below swagger validation errors will not break the existing flows so we can approve this PR.

##[error]The operation has been deleted. This change breaks existing flows. ValuePath: operation/TriggerRequestCreated Source: NewSwagger
##[error]The operation has been deleted. This change breaks existing flows. ValuePath: operation/TriggerRequestStatusChanged Source: NewSwagger