Use lazy import for generate_mapping_docs by moving it in setup function

[pankajastro]

closes: https://github.com/astronomer/oss-integrations-private/issues/286

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.84%. Comparing base (b8f77b3) to head (1ba5a30).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2188      +/-   ##
==========================================
+ Coverage   97.46%   97.84%   +0.38%     
==========================================
  Files          94       94              
  Lines        6038     6038              
==========================================
+ Hits         5885     5908      +23     
+ Misses        153      130      -23     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

This PR improves the documentation build process by converting the generate_mapping_docs import from an eager top-level import to a lazy import within a Sphinx setup function. This change allows the documentation to build gracefully even when Airflow dependencies are not installed, making local development easier.

Key Changes:

• Moved generate_mapping_docs import and execution from module-level to inside a Sphinx setup function
• Added error handling to catch and warn about missing dependencies instead of failing the build
• Made the paths explicit by constructing absolute paths to templates and output directories

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The Sphinx setup function should return a metadata dictionary. This is a best practice that helps Sphinx understand the extension's requirements and capabilities. Consider adding a return statement at the end:

return {
    'version': '0.1',
    'parallel_read_safe': True,
    'parallel_write_safe': True,
}

Suggested change

	)
	)
	return {
	'version': '0.1',
	'parallel_read_safe': True,
	'parallel_write_safe': True,
	}

[Copilot]

The error message says "If Airflow is not available" but the actual import is from docs.generate_mappings. The import could fail for reasons other than Airflow not being available (e.g., missing jinja2). Consider making the error message more accurate:

# If dependencies are not available, skip generating mapping docs
# This can happen during local development if dependencies aren't fully installed

Suggested change

	# If Airflow is not available, skip generating mapping docs
	# This can happen during local development if dependencies aren't installed
	import warnings
	warnings.warn(
	f"Could not generate mapping docs: {e}. "
	"Make sure Airflow is installed (pip install -r docs/requirements.txt). "
	# If required dependencies are not available, skip generating mapping docs
	# This can happen during local development if all documentation dependencies aren't installed
	import warnings
	warnings.warn(
	f"Could not generate mapping docs: {e}. "
	"Make sure all documentation dependencies are installed (pip install -r docs/requirements.txt). "

[pankajastro]

The CI is green now, so we do not need this