Add support for configs, secrets, networks and replicas for DockerSwarmOperator

[enima2684]

This PR adds the following functionality to the DockerSwarmOperator :

• support for setting secrets and configs exposed to the started service
• support for specifying networks that can be joined by the containers of the service
• support for specifying the number of replicas for the swarm service

This features are essential in order to run the DockerSwarmOperator on a production environment with shared secrets, configs and networks.

The issue #7955 also mentions the need for this features.

P.S: this is my first contribution to Airflow. Tried to follow the contribution guidelines. Forgive any missed step and looking forward for your feedback !

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

Fixed

[uranusjr]

We now have

• from docker import types
• from docker.types import ...
• from docker.types.services import ...

Around the same proximity. They should be somewhat unified. I think from docker import types can be used to access everything?

[enima2684]

Fixed the imports as asked :)

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

[akki]

Great feature addition!

Left a couple of comments - hope they're helpful.

[enima2684]

Hi @akki,
Thanks for your review and comments :)
I think we have covered them all and needed fixes are done.
Can you please approve the PR if all ok for you ?
Many thanks

[boring-cyborg]

Awesome work, congrats on your first merged pull request!

[akki]

Great. Congrats @enima2684 & welcome to the committers clan! 😉