feat(framework): Allow ServerAppExecPlugin to support both flwr-serverapp and flwr-simulation

[panh99]

Last missing piece to make one SuperLink support both runtimes.

[Copilot]

Pull request overview

This PR consolidates SuperExec support so a single ServerAppExecPlugin can launch either flwr-serverapp or flwr-simulation based on a run’s run_type, enabling one SuperLink to support both runtimes.

Changes:

• Remove SimulationExecPlugin and route simulation launches through ServerAppExecPlugin.
• Update flower-superexec wiring and ExecPluginType to drop the dedicated simulation plugin type.
• Adjust simulation/server entrypoints and tests to use the unified plugin approach.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
framework/py/flwr/supercore/superexec/plugin/simulation_exec_plugin.py	Removes the dedicated simulation exec plugin.
framework/py/flwr/supercore/superexec/plugin/serverapp_exec_plugin.py	Adds run-type-based selection of flwr-serverapp vs flwr-simulation.
framework/py/flwr/supercore/superexec/plugin/base_exec_plugin_test.py	Updates test run fixture to include run_type.
framework/py/flwr/supercore/superexec/plugin/init.py	Stops exporting SimulationExecPlugin.
framework/py/flwr/supercore/cli/flower_superexec.py	Removes simulation plugin type mapping.
framework/py/flwr/simulation/app.py	Uses ServerAppExecPlugin and serverapp plugin type for the deprecation path.
framework/py/flwr/server/app.py	Always starts flower-superexec with --plugin-type serverapp.
framework/py/flwr/common/constant.py	Removes ExecPluginType.SIMULATION.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.