feat(fly-io): Added fly.io template files

[john-fueled]

Added fly.io template files for a deployable Dockerfile and Github actions.

Why was this change necessary?

Spin up a hosted development environment fast.

How does it address the problem?

Adds fly.io as an optional deployment destination.

Are there any side effects?

The local and dev Dockerfiles do not have the same configuration that Fly.io expects. When deploying the dev Dockerfile, Fly.io deploys hang due to the entrypoint script running the gunicorn command which never exits. Therefore a separate compose/fly folder has the necessary changes to pass the build process.

Addresses #466

[theskumar]

Possible to use the existing docker files?

https://github.com/Fueled/django-init/blob/main/%7B%7Bcookiecutter.github_repository%7D%7D/compose/dev/django/celery/worker/start

[kasparszarinovs]

@CuriousLearner @sun337 @saurabh-fueled are we wanting to keep a Fly.io template in this, or should this be closed?
I personally think Fly.io is probably not a bad option for dev phase deploiyments.

[CuriousLearner]

I think this is a good addition since we removed Heroku sometime ago.

[CuriousLearner]

Oops! Pardon me. Heroku is still there. We can add fly.io similar to how Heroku is added.

However, I think we need to settle down on either poetry or requirements.txt, otherwise, we are creating a matrix of options that will be difficult to maintain. Please let me know your thoughts.

[theskumar]

We go with poetry.