build(deps): bump org.apache.axis2:axis2-transport-http from 1.7.0-SNAPSHOT to 1.8.0 in /modules/samples/dynamicclient/client

[dependabot]

Bumps org.apache.axis2:axis2-transport-http from 1.7.0-SNAPSHOT to 1.8.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[cortlepp]

@robertlazarski regarding this PR (and also #1076) I have been wondering how we should treat our "samples": Some of them we build with maven, some we don't (like for example the ones mentioned in this or the other PR).

1. Should we not build the samples? Doing so would in my mind ensure that the samples still work (at least on a basic level) and then we probably also wouldn't have had this specific versioning problem here, because I guess the version updates would then work like they do everywhere else. Is it intentional that we don't build all of the samples?
2. If we don't want to build the samples, maybe it does make more sense to then refer to stable versions (of our own releases) instead of snapshots.

[robertlazarski]

@dependabot rebase

[robertlazarski]

@cortlepp I had no idea this sample even existed. Anyways, we should keep the samples updated so that they are not distributed with known security violations.

Yet this case shows that some of these samples probably have limited usefulness in 2025 and beyond. Best we can do is merge the PR and move on.

[robertlazarski]

@cortlepp forgot to mention, I did a dependabot rebase to 2.0.0, obviously the PR from 1.7.0 to 1.8.0 was wrong anyways

[cortlepp]

replaced by #1101

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.