feat: Add support for Preserve Repository During Deployment in API

[ahmadw13]

Changes

This PR exposes Preserve Repository During Deployment to the API and allows turning it on during application creation and updating application settings

Issues

• fixes: Ability to support set Preserve Repository During Deployment option on API #7108
  Exposing Preserve Repository During Deployment to API #8341

Category

• New feature

AI Usage

• AI is NOT used in the process of creating this PR

Steps to Test

• Step 1 – Setup API access and client
• Step 2 – Create an application at /api/v1/applications/private-deploy-key POST or to any repo based application and in the body include requireds items and is_preserve_repository_enabled to true

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have tested the changes thoroughly and am confident that they will work as expected without issues when the maintainer tests them

[github-actions]

This PR did not pass quality checks so it will be closed. If you believe this is a mistake please let us know.

[gitguardian]

⚠️ 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
26963785	Triggered	Company Email Password	548dc51	.claude/skills/pest-testing/SKILL.md	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.}