Add a microservices based sample app to test enablement

[AsakerMohd]

Adding a microservices based sample app to help us test enablement for the python integration. Most of the code is boiler plate code created by Django.
The most important code to look at is inside the MainService folder for each microservice. Those are under the urls.py, views.py and the models.py.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[thpierce]

Most of the code is boiler plate code created by Django.

Can you be more specific:

• What commands did you use to generate code?
• What files were generated?
• What files did you modify?

[AsakerMohd]

Most of the code is boiler plate code created by Django.

Can you be more specific:

* What commands did you use to generate code?

* What files were generated?

* What files did you modify?

Starting a Django project using intellij generates the files. Intellij runs django-admin startproject <project_name> under the hood.

All the files were generated except docker specific files and my.cnf which is mysql config file for django web server to connect to the DB.

The files that were modified are under the MainService folder for each microservice. The specific files are urls.py, views.py and the models.py.

[thpierce]

Still need to review the urls.py and views.py files.

[zzhlogin]

For all code files, I think we need to add a header:

aws-otel-python-instrumentation/checkers/file_header_checker.py

Line 1 in e2d5249

# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.

Since you are adding new folders, you should setup eachdist.py and eachdist.ini, to allow lint and test workflow apply to all files/tests.