Revert "chore(agw): Move script-only dependencies to scripts folders (#12773)"

[nstng]

This reverts commit 059393d.

Summary

See #13190.

Problem

• In Move python module code to script folders #12754, chore(agw): Move script-only dependencies to scripts folders #12773 python files that are only used in scripts were moved from service folders to the script folder.
• These files are not added to magma.deb, i.e., the scripts will raise ModuleNotFoundError.

Solution Here

• chore(agw): Move script-only dependencies to scripts folders #12773 is reverted for now - there is currently no suitable location for script dependencies in magma.deb

Test Plan

In magma VM

• ~/magma/lte/gateway $ ./release/build-magma.sh -h 123 --commit-count 23 -t RelWithDebInfo --cert $MAGMA_ROOT/.cache/test_certs/rootCA.pem --proxy $MAGMA_ROOT/lte/gateway/configs/control_proxy.yml --os ubuntu
• move magma_1.8.0-1657013498-123_amd64.deb (timestamp will vary) to a VM where magma can be installed

In Install VM

• sudo apt install ./magma_1.8.0-1657013498-123_amd64.deb
• execute health_cli.py or agw_health_cli.py
• see that ModuleNotFoundError on scripts is not raised

NOTE

• currently there is still a ModuleNotFoundError - on docker
  • workaround: sudo apt install python3-docker
• this is currently handled in fix(agw): Fixed root_versions #13192

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

feg-workflow

    2 files  203 suites   39s ⏱️
374 tests 374 ✔️ 0 💤 0 ❌
388 runs  388 ✔️ 0 💤 0 ❌

Results for commit a0f625b.

♻️ This comment has been updated with latest results.

[github-actions]

dp-workflow

18 tests   18 ✔️  4m 21s ⏱️
  2 suites    0 💤
  2 files      0 ❌

Results for commit a0f625b.

♻️ This comment has been updated with latest results.

[github-actions]

cloud-workflow

990 tests   990 ✔️  2m 17s ⏱️
355 suites      0 💤
    7 files        0 ❌

Results for commit a0f625b.

♻️ This comment has been updated with latest results.

[github-actions]

agw-workflow

580 tests   576 ✔️  6m 30s ⏱️
    2 suites      4 💤
    2 files        0 ❌

Results for commit a0f625b.

♻️ This comment has been updated with latest results.

[LKreutzer]

Lgtm. I restarted the failed agw-workflow (it was the flaky mme test 11).