Adjust the design of FedML Python Agent to a decentralized architecture that supports Launch Master, Launch Slave, Deploy Master, and Deploy Slave at the same time. #3

	# This is a basic workflow to help you get started with Actions

	name: CI-federate

	# Controls when the workflow will run
	on:
	# Triggers the workflow on push or pull request events but only for the master branch
	schedule:
	# Nightly build at 12:12 A.M.
	- cron: "0 10 /1 *"
	pull_request:
	branches: [ master, dev/v0.7.0 ]

	# Allows you to run this workflow manually from the Actions tab
	workflow_dispatch:

	# A workflow run is made up of one or more jobs that can run sequentially or in parallel
	jobs:
	federate:
	strategy:
	fail-fast: false
	matrix:
	os: [ Linux, Windows ]
	arch: [X64]
	python-version: ['python3.8', 'python3.9', 'python3.10', 'python3.11']

	runs-on: ["${{ matrix.python-version }}","${{ matrix.os }}"]
	timeout-minutes: 5
	steps:
	- name: Checkout fedml
	uses: actions/checkout@v3

	- name: pip_install
	run: \|
	cd python
	pip install -e ./

	- name: federate_job_in_test_env
	run: \|
	cd python
	bash tests/test_federate/test_federate.sh
	echo "Federate example has been tested successfully!"

Provide feedback