docs: add api ref using mkdocstrings

[julesbertrand]

Description

Related Issue

Type of Change

• 🚀 New feature (non-breaking change which adds functionality)
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🔐 Security fix
• ⚙️ CI / CD update
• 📚 Examples / docs / tutorials / dependencies update
• 💥 Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make format-code.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.
• If my change requires a change to docs, I have updated the documentation accordingly.

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Code Smell The URL in the docstring should be enclosed in angle brackets to render correctly in some documentation tools. Consider changing See https://cloud.google.com/python/docs/reference/aiplatform/latest/google.cloud.aiplatform.PipelineJob`` to See <https://cloud.google.com/python/docs/reference/aiplatform/latest/google.cloud.aiplatform.PipelineJob>.

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Enclose the URL in angle brackets to ensure it renders correctly as a clickable link Ensure the URL in the docstring is enclosed in angle brackets to render it correctly as a clickable link in most documentation generators. deployer/pipeline_checks.py [149] -to VertexAI. See `https://cloud.google.com/python/docs/reference/aiplatform/latest/google.cloud.aiplatform.PipelineJob` +to VertexAI. See <https://cloud.google.com/python/docs/reference/aiplatform/latest/google.cloud.aiplatform.PipelineJob> Suggestion importance[1-10]: 8 Why: Enclosing the URL in angle brackets is a best practice for documentation, ensuring it renders correctly as a clickable link in most documentation generators. This improves the readability and usability of the documentation.	8