Resolve WIT-278 "Release for MWAA SP"

# New features and improvements

Release notes

# Related issue

Closes WIT-278

# Definition of Done for Feature/Hotfixes

## All Developments

- [x] Feature was implemented as per the requirements
- [x] If some code parts are complex they must be commented with code documentation
- [x] CI/CD is successful
- [x] Code coverage is not reduced, any new code is covered
- [x] E2E/integration tests are successful (whether run locally or in CI/CD)
- [x] If dependencies were changed, be sure that they will not impact the project, that their license is compatible, and that they introduce no vulnerabilities
- [x] Documentation have been updated
  * Documentation has been updated with explanation of the new feature if it is user-facing (eg component now has additional setting) or it impacts him in some other way (eg optional field that becomes mandatory)
  * If it is a breaking change, we have documented it as such in the MR description in a "Breaking Changes" section
- [x] Check that you are not affecting any existing environments with these changes, especially the Sandbox/Playground. This means that merging it to master and deploying it to these environments will not break them and **no manual operations that are not reported in the documentation will be needed**
- [x] Check that nothing is out of order and nothing problematic is included in the changes (sensitive information, credentials, customer information or other intellectual property) as they could end up being public (we have Open Source SP already published and automatically mirrored)
- [x] Security, Authentication and Authorization have been considered. No SQL injection, tokens handling, RBAC integration. Common security vulnerabilities identified and resolved

## API Development

- [x] Semantic of API has been checked, it is comprehensible, meaningful, with no redundant information and user oriented
- [x] Meaningful unit and integration tests are present
- [x] API Parameters are checked and errors are handled
- [x] Returned errors are meaningful to the user
- [x] API contract has been defined and documented. Documentation means explaining the meaning of all fields and including at least one example
- [x] Exceptions and errors are handled, without letting the underlying framework to respond with a generic Internal Server Error
- [x] API Performance has been assessed and is good for real world use cases. Database accesses have been optimized.
- [x] API is logging in compliance with audit standards, presence of sensitive information for GDPR has been assessed and removed or managed in case is needed

## DB Development

- [x] The database schema is designed to accurately represent the data model and meet the requirements
- [x] Tables, relationships, and constraints (e.g. primary keys, foreign keys, unique constraints) are defined appropriately and following a common convention
- [x] Normalization principles are applied to eliminate data redundancy and ensure data integrity
- [x] Schema semantic is meaningful
- [x] Fields naming are following naming convention ( Ex. camelCase or snake_case)
- [x] No fields with mixed behaviors and meaning. If a field is representing an enum, enum values are strongly mutually exclusive
- [x] Data Types have been reviewed and they are a good fit for each field
- [x] Indexes are defined to optimize query performance for frequently accessed data, paying attention to do not affect too much write path and the overall complexity
- [x] Sensitive data is stored securely, encrypted if required, and access is restricted to authorized users
- [x] Backup and restore procedures have been updated to introduce new or changed tables
- [x] Migration scripts to upgrade and downgrade the database have been implemented and tested

Author: cristianastorino-agilelab

RELEASE_NOTES.md

@@ -0,0 +1,96 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## v1.0.0
+
+### Commits
+
+- **[WIT-249] Some SPs provisioning status endpoint incorrectly reports completed for non existent tokens**
+  > 
+  > ##### New features and improvements
+  > 
+  > - Aligns the interface specification version to version 2.2.0
+  > - Includes a Postman collections with some examples
+  > 
+  > ##### Related issue
+  > 
+  > Closes WIT-249
+  > 
+  > 
+
+- **[WIT-249] Some SPs provisioning status endpoint incorrectly reports completed for non existent tokens**
+
+- **Resolve WIT-287 "Update mwaa deployment"**
+
+- **[WIT-204] HLD documentation for MWAA SP**
+
+- **[WIT-195] API version field in OpenAPI spec is set to implementing server version**
+
+- **[WIT-199] Documentation**
+
+- **Resolve WIT-50 "Update mwaa helm chart"**
+
+- **[WIP] feature: custom-changes-mwaa**
+
+- **[#8] Resolve "Add file name prefix in the unprovision method"**
+
+- **Resolve "Minor improvements"**
+  > 
+  > ##### New features and improvements
+  > 
+  > - Inserted a prefix folder dags and source inside the mwaa manager `executeProvision` function call
+  > - Prefix also for the dag file name that ends up in the airflow so it looks like $componentIdentifier(without componentName).$dag_name
+  > 
+  > ##### Related issues
+  > 
+  > Closes #7
+
+- **[#6] Resolve "Deploy MWAA sp"**
+  > 
+  > ##### New features and improvements
+  > 
+  > - Implemented k8s deployment
+  > - Changed s3Client initialization in order to include WebIdentity
+  > 
+  > ##### Related issues
+  > 
+  > Closes #6
+
+- **[#5] Resolve "Fix a little bug inside provision and unprovision"**
+  > 
+  > ##### Bugs fixed
+  > 
+  > - Fixed a bug for subfolders handling
+  > 
+  > ##### Related issues
+  > 
+  > Closes #5
+
+- **[#2] Resolve "Import aws sdk the right way"**
+  > 
+  > ##### New features and improvements
+  > 
+  > - Added provision API
+  > - Added unprovision API
+  > - Imported aws sdk library
+  > - Added an example of descriptor to pass to the provision and unprovision API (it is called pr_descriptor_mwaasp.yaml)
+  > 
+  > ##### Related issues
+  > 
+  > Closes #2
+
+- **[#3] Resolve "Make akka http request to airflow"**
+  > 
+  > ##### New features and improvements
+  > 
+  > - Added `/provision` API
+  > - Added docker-compose to start airflow locally
+  > - Set up the logs
+  > - Updated README with how to run airflow locally
+  > 
+  > ##### Related issues
+  > 
+  > Closes #3
+
+- **Init**