Refactor: Remove server and proxy modules from Sumaform (legacy for SUMA 4.3)

[srbarrios]

Description:

As part of the ongoing effort to simplify and modernize sumaform, I propose removing the server and proxy modules from the master branch. These modules are only used by the SUMA 4.3 product version, which relies on non-containerized components and is approaching its End-of-Life (EoL) in less than a year.

Rationale

• Maintenance overhead: These modules introduce legacy complexity and aren't aligned with the containerized direction of newer versions.
• Low usage: They are exclusively used in test suites for 4.3, which will be deprecated soon.
• Cleaner codebase: Removing them will lighten the project, make it easier to maintain, and reduce cognitive load for new contributors.

Proposal

1. Create a Git Tag, e.g., 4.3-legacy, on the current commit that supports these modules.
2. Continue running all SUMA 4.3 test suites based on this tag to avoid regressions.
3. Remove the server and proxy modules from the master branch.

This way, we keep 4.3 test coverage intact while focusing sumaform development on modern and actively maintained versions.

Feedback welcome before proceeding with the cleanup!

[ktsamis]

I'm not sure we should do this, we might do updates in the code that would be needed in 4.3 states and freezing in the commit would cause trouble. I would postpone this until 4.3 is out of support completely. I'm not sure of the effort though or even if it's possible that we will need to touch this code again until then. So for me it would be ok to try this and worst case we revert the removal if we need to touch this code