Implement CI test for python driver

[MuhammadTahaNaveed]

What I did

• Implemented a CI workflow for python driver that ensures that any PR/commit that modifies files under age/drivers/python is passing the tests.
• Moved docker-compose.yaml file in age/drivers/golang to age/drivers, because this is required to instantiate a postgres instance needed for unit testing.
• Modified host address of connection params to localhost in 'test_age_py.py' to connect to postgres instance running in docker container.

Additional Context

This workflow will only run if their is a modification in files under age/drivers/python.

[jrgemignani]

@MuhammadTahaNaveed While I am all for these automated tests, I need to put a hold on them for the moment.

Apache org is moving away from Travis CI and we aren't sure of what direction we need to go with these tests - both current and new ones. That is, do they have another CI product they want us to use in place of Travis or can we still continue to use Travis.

If you would like to look into that, that would be really helpful and appreciated

[MuhammadTahaNaveed]

Ok 😅. Is their any forum or something like that where Apache informs about these things ? Btw, this workflow is not using travis, it is using github actions.

[jrgemignani]

Ok 😅. Is their any forum or something like that where Apache informs about these things ? Btw, this workflow is not using travis, it is using github actions.

They informed us via email. Our options are Github actions or Jenkins. Jenkins supports ARM whereas Github actions doesn't.