Selenium suites: replace Java AMQP 1.0 client with a JavaScript one (backport #12786)

[mergify]

Proposed Changes

Given that selenium tests are written in javascript, it makes more sense and it is clearer to use a amqp10 client in javascript.

---

This is an automatic backport of pull request #12786 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 0ba194a has failed:

On branch mergify/bp/v4.0.x/pr-12786
Your branch is up to date with 'origin/v4.0.x'.

You are currently cherry-picking commit 0ba194ae53.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   selenium/Dockerfile
	deleted:    selenium/amqp10-roundtriptest/pom.xml
	deleted:    selenium/amqp10-roundtriptest/run
	modified:   selenium/package.json
	new file:   selenium/test/amqp.js

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: selenium/amqp10-roundtriptest/src/main/java/com/rabbitmq/amqp1_0/RoundTripTest.java
	both modified:   selenium/test/authnz-msg-protocols/amqp10.js
	deleted by us:   selenium/test/connections/amqp10/sessions-for-monitoring-user.js

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[michaelklishin]

@MarcialRosales can you please resolve these conflicts? You have all the context.