feat(sage-people): Add support for Sage People

[ChoqueCastroLD]

EXT-732

---

This PR introduces a new integration for Sage People, including documentation, configuration, and visual assets. It adds the 'sage-people' provider to providers.yaml with full credential and connection configuration, and supplies new documentation files, a Connect guide, prebuilt tooling/use cases stubs, and the Sage People logo for the UI.

Key Changes: • Added 'sage-people' provider to packages/providers/providers.yaml with required API key/domain configuration, OAuth/authorization details, and endpoint verification. • Created new documentation and integration guide for Sage People (docs-v2/integrations/all/sage-people.mdx, connect.mdx), including setup prerequisites and OAuth instructions. • Added stubs for prebuilt tooling and use cases for Sage People (snippets/generated/sage-people/PreBuiltTooling.mdx, PreBuiltUseCases.mdx). • Added new SVG logo asset for Sage People (public/images/template-logos/sage-people.svg).

Affected Areas: • Integration provider definitions • Integration documentation and guides • UI assets for provider logos • Prebuilt use case/tooling documentation

This summary was automatically generated by @propel-code-bot

[linear[bot]]

EXT-732 Add support in Nango for Sage People

[ChoqueCastroLD]

Moved to draft because needs testing and rebase

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
17919377	Triggered	Generic Password	d660e75a0f8379f069b5a7860ca36d430dee356d	.github/workflows/managed-release.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[hassan254-prog]

closing in favor of 4423