The 404 of death: Dump jersey effective configuration on startup

If anything goes wrong in any way with jersey, the developer gets a 404 Not Found and zero error message.

There has got to be a better way than this:

https://stackoverflow.com/questions/61103553/jersey-jax-rs-application-returns-404
https://stackoverflow.com/questions/19711177/jersey-gives-404-not-found-on-valid-service?rq=4
https://stackoverflow.com/questions/23946308/jax-rs-2-using-jersey-client-getting-http-404-not-found-but-same-url-is-work?rq=4
https://stackoverflow.com/questions/29315062/404-error-with-jersey-rest-service-on-tomcat?rq=4
https://stackoverflow.com/questions/33734671/java-rest-api-returns-http-status-404?rq=4
https://stackoverflow.com/questions/35451267/keep-getting-404-with-jax-rs-jersey-and-tomcat-8-what-am-i-doing-wrong?rq=4
https://stackoverflow.com/questions/38938535/rest-apis-return-404-not-found-when-path-configured-in-web-xml?rq=4
https://stackoverflow.com/questions/43519920/jersey-application-deployed-on-tomcat-returns-404?rq=4
https://stackoverflow.com/questions/43879815/web-service-with-jersey-return-only-404?rq=4
https://stackoverflow.com/questions/48063955/im-getting-404-error-when-trying-to-access-rest-webapp?rq=4
https://stackoverflow.com/questions/62413076/javax-ws-rs-notfoundexception-http-404-not-found-occurring-after-request?rq=4

Is there a way to dump the effective configuration of jersey on startup to the servlet log file.

Most specifically, without any hit-and-miss java logging config (which is it's own nightmare of endless guessing), is there a method that prints out every application, containing every path, containing every method, etc etc, and crucially - what the path is actually called.

Not what the end user might infer the path might be called, but the actual concrete path for that application deployment.