Add Perplexity integration attribution

[qirh]

What is this PR about?

Perplexity would like to identify requests made through Dokploy. This adds X-Pplx-Integration: dokploy to Dokploy's existing Perplexity provider requests without changing authentication, payloads, or routing.

Checklist

• This uses a dedicated branch based on canary.
• I have read the pull request guidance in CONTRIBUTING.md.
• The Perplexity provider was constructed locally and produced the normalized outbound header x-pplx-integration: dokploy.

Issues related (if applicable)

Not applicable.

Screenshots (if applicable)

Not applicable.

Confidence Score: 5/5

The PR appears safe to merge because the attribution header is narrowly scoped to the existing Perplexity provider branch and does not alter authentication or routing.

Summary

Adds Perplexity integration attribution to outbound requests.

• Supplies X-Pplx-Integration: dokploy through the existing OpenAI-compatible provider configuration.
• Leaves the provider endpoint, authentication header, payload, and routing unchanged.

_{Reviews (1) · Last reviewed commit: "feat(ai): add Perplexity integration att..."}