Add API documentation using autodoc and autosummary

[Aditi2424]

This PR adds comprehensive API documentation for SageMaker Python SDK v3 using Sphinx autodoc and autosummary.

Changes

• Configure Sphinx autodoc to import actual sagemaker modules instead of mocks
• Add API reference pages for all four main modules (core, train, serve, mlops)
• Include all v3-examples in documentation navigation
• Reduce build warnings from 2167 to under 50

Benefits

• Users can now see real class signatures, methods, and docstrings
• API documentation shows actual functionality instead of empty mock objects
• Comprehensive coverage of all available classes and functions
• Clean build process with minimal warnings

The API documentation now provides useful, actionable information for developers using the SageMaker Python SDK v3.

[amazon-q-developer]

Code Review Summary

This PR adds comprehensive API documentation for SageMaker Python SDK V3 using Sphinx autodoc and autosummary. While the overall approach is sound, there are several critical configuration issues that must be addressed before merge.

Critical Issues Found:

1. 🛑 Sphinx Configuration Errors - Duplicate html_theme_options and suppress_warnings definitions that overwrite important settings
2. 🛑 Security Vulnerability - XSS risk in JavaScript feedback component using insertAdjacentHTML with template literals
3. Logic Error - Duplicate variable assignment in notebook example that causes confusion

Issues Summary:

• Configuration Issues: 2 critical Sphinx configuration problems that will break documentation builds
• Security Issues: 1 XSS vulnerability in JavaScript code
• Code Quality: 1 variable assignment issue in example notebook
• Dependency Management: Missing version constraints in requirements.txt

Recommendations:

1. Fix the duplicate configuration definitions in docs/conf.py
2. Replace insertAdjacentHTML with safer DOM manipulation methods
3. Add proper version constraints to all dependencies
4. Resolve the duplicate variable assignment in the notebook

The documentation structure and content are well-organized, but these configuration and security issues must be resolved to ensure a successful and secure documentation build process.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[amazon-q-developer]

Add version constraints for all dependencies to ensure reproducible builds. Missing version constraints can lead to build failures when newer incompatible versions are released.

Suggested change

	ipykernel
	jupyter
	pandas
	numpy
	sphinx>=4.0.0
	sphinx-book-theme>=1.0.0
	myst-nb>=0.17.0
	jupyter-book>=0.15.0
	sphinx-design>=0.4.0
	ipykernel>=6.0.0
	jupyter>=1.0.0
	pandas>=1.3.0
	numpy>=1.21.0

[amazon-q-developer]

🛑 Security Vulnerability: Using insertAdjacentHTML with template literals creates a potential XSS vulnerability. User input could be injected into the HTML template. Use createElement and textContent instead for safer DOM manipulation.

[amazon-q-developer]

Variable s3_checkpoint_path is assigned twice with different values. The first assignment from get_s3_manifest() is overwritten by the second assignment from describe_training_response["CheckpointConfig"]["S3Uri"]. This creates confusion and potential runtime errors.

Suggested change

	"s3_checkpoint_path = get_s3_manifest(training_output_s3_uri)\n",
	"\n",
	"\n",
	"bedrock_client = boto3.Session().client(service_name=\"bedrock\", region_name=REGION)\n",
	"\n",
	"\n",
	"s3_checkpoint_path = describe_training_response[\"CheckpointConfig\"][\"S3Uri\"]\n",
	s3_checkpoint_path = get_s3_manifest(training_output_s3_uri)
	bedrock_client = boto3.Session().client(service_name="bedrock", region_name=REGION)
	# Use the checkpoint path from the manifest
	# s3_checkpoint_path = describe_training_response["CheckpointConfig"]["S3Uri"] # Remove this duplicate assignment