Remove aproxy installation and add proxy support in workload

[swetha1654]

Applicable spec:

Overview

Remove aproxy installation in the charm and inject proxy values from the model config into the workload process.

Rationale

Juju Events Changes

Module Changes

Library Changes

Checklist

• The charm style guide was applied
• The contributing guide was applied
• The changes are compliant with ISD054 - Managing Charm Complexity
• The documentation for charmhub is updated.
• The PR is tagged with appropriate label (urgent, trivial, senior-review-required, documentation)
• The docs/changelog.md is updated with user-relevant changes in the format of keep a changelog v1.1.0
• The application version is incremented in app/pyproject.toml

[yanksyoon]

Would proxy configuration be required to be passed into network calls? Thanks :D

[Copilot]

@yanksyoon I've opened a new pull request, #188, to work on those changes. Once the pull request is ready, I'll request review from you.

[cbartz]

TY @swetha1654 ! I think what is missing is to add the proxy env vars also to the charm related network calls, like pipx or apt . The integration test is currently working because it runs on a runner that uses aproxy on the host, which forwards all traffic to a proxy. You could modify the integration test by adding a call sudo nft delete chain ip aproxy prerouting to remove routing to the aproxy on the host. I assume the tests will fail in that case.

[cbartz]

TY! Two comments related to passing over the whole env. Otherwise looks great!