Publish documentation to github pages

[d-ryan-ashcraft]

As we migrate to the new public repo, we need to update our documentation needs to be brought into the repository and to have a new job that will publish it. Some of the prior docs had some complex subfolders with multiple aissemble references. If possible, it would be nice to clean that up in the process of working this ticket.

Since we publish some schemas for data lineage via github pages, we'll also need to ensure those resolve in a way that matches the codebase for 1.7.0.

Definition of Done

• Migrate over existing documentation into codebase (split into tranches below)
• ✅ Leverage GitHub Action to publish to GitHub pages
• ✅ Add Badge for documentation to the top of the page (with other useful, common badges)
• ✅ Update main readme file to remove link placeholders and fill in documentation section with more topical information

Documentation Tranches

Tranche 1

• ✅ GitHub Action
• ✅ Badges
• ✅ General Antora Setup
• ✅ Landing page
• ✅ Configuration page
• ✅ Maven Configuration page
• ✅ Archetype page

Tranche 2

• ✅ Versions
• ✅ aiSSEMBLE Baseline Process
• ✅ aiSSEMBLE Approach
• ✅ Add Pipelines
• ✅ Pipeline Metamodel

Tranche 3

• ✅ Data Delivery Pipelines
• ✅ Machine Learning Pipeline
• ✅ Containers
• ✅ Testing
• ✅ Lineage Overview
• ✅ Model Lineage
• ✅ Data Lineage

Tranche 4

• ✅ CI/CD
• ✅ Spark Job Guide
• ✅ Semantic Data
• ✅ Dictionary Metamodel
• ✅ Alerting
• ✅ Bias Detection
• ✅ Data Access

Tranche 5

• ✅ Spark Data Delivery Pipelines
• ✅ PySpark Data Delivery Pipelines
• ✅ Data Encryption
• ✅ Data Profiling
• ✅ Data Validation
• ✅ Drift Detection
• ✅ File Storage

Tranche 6

• ✅ Messaging
• ✅ Post Actions
• ✅ Security
• ✅ Path to Production
• ✅ Databricks
• ✅ Record Metamodel
• ✅ Type Metamodel

Tranche 7

• ✅ Shared Python Module
• ✅ Python Debugging
• ✅ Local Mulit-Node
• ✅ Poetry Python Pipeline
• ✅ Sagemaker Training
• ✅ Configuration Store