Merge main into staging

[nrichers]

Pull Request Description

What and why?

We got a rare merge conflict between main and staging which this PR fixes.

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

PR Summary

This PR enhances the integrations section of the documentation by introducing several new and improved integration examples and updating the sidebar configuration. The key changes include:

• Modifications in the sidebar YAML file to change how integration examples are referenced. Instead of a single file path, the new format uses a detailed listing with a separate set of content files for each integration example.

• Addition of detailed documentation pages for various integrations, such as:

  • Creating Jira tickets via HTTP requests
  • Creating ServiceNow incidents using webhooks
  • Synchronizing models with AWS SageMaker and AWS Bedrock
  • Synchronizing models with GitLab
  • Integrating with Databricks including a quickstart guide, detailed configuration steps, and how to link records
  • Using webhooks to start or resume workflows

• Updates to the Databricks integration documentation, including an explanation of how Unity Catalog resources are synchronized and a mermaid diagram to illustrate the data flow.

These changes provide clearer guidance on configuring the connections and workflows, and offer a more structured and detailed approach to integrating with external systems using the platform.

Test Suggestions

• Verify that the updated sidebar correctly renders the new file structure and navigation links for integration examples.
• Check that all new integration example pages render properly in different browsers and on various devices.
• Test the code samples (e.g., HTTP request payloads, webhook configurations, curl commands) to ensure they are correct and lead to expected behaviors in a staging environment.
• Validate that images (screenshots) referenced in the documentation are loading correctly and have appropriate alt texts.

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

[github-actions]

Lighthouse check results

⚠️ WARN: Average accessibility score is 0.87 (required: >0.9) — Check the workflow run

Show Lighthouse scores

Folder depth level checked: 0

Commit SHA: 7257fa4

Modify the workflow to check a different depth:

• 0: Top-level navigation only — /index.html, /guide/guides.html, ...
• 1: All first-level subdirectories — /guide/.html, /developer/.html, ...
• 2: All second-level subdirectories — /guide/attestation/*.html, ...

Page	Accessibility	Performance	Best Practices	SEO
/developer/validmind-library.html	0.85	0.69	1.00	0.82
/get-started/get-started.html	0.85	0.70	1.00	0.73
/guide/guides.html	0.85	0.69	1.00	0.82
/index.html	0.93	0.69	1.00	0.82
/releases/all-releases.html	0.86	0.70	1.00	0.73
/support/support.html	0.91	0.66	1.00	0.82
/training/training.html	0.85	0.66	0.96	0.73