fix: don't bind Jetty if server.port is -1

[Dogacel]

Motivation:

Make behavior in Tomcat and Jetty consistent when server.port is set to -1.

Modifications:

• Configure JettyServlet to remove the binding to a random port if server.port is -1 and an armeria connector is added.

Result:

• Closes #5039.
• Jetty no longer spawns the servlet on a random port if server.port is assigned to -1.

[github-actions[bot]]

🔍 Build Scan® (commit: 13bbc65591eb6ca39e8ca442e0b281dc01ef4582)

Job name	Status	Build Scan®
build-ubicloud-standard-16-jdk-8	✅	https://ge.armeria.dev/s/qqyyrxqifpaxc
build-ubicloud-standard-16-jdk-21-snapshot-blockhound	✅	https://ge.armeria.dev/s/3dduxdb72k46a
build-ubicloud-standard-16-jdk-17-min-java-17-coverage	✅	https://ge.armeria.dev/s/mvkdvlrwchfyw
build-ubicloud-standard-16-jdk-17-min-java-11	✅	https://ge.armeria.dev/s/il6bb5mhi6cxc
build-ubicloud-standard-16-jdk-17-leak	✅	https://ge.armeria.dev/s/22rxwpe5ry57o
build-ubicloud-standard-16-jdk-11	✅	https://ge.armeria.dev/s/kkf4o2rcdk52c
build-macos-latest-jdk-21	✅	https://ge.armeria.dev/s/xw4y4hlvugjmq