Ban org.ow2.asm:asm in non-deployment modules

[ppalaga]

Before #487, we were banning org.ow2.asm:asm in some modules. We should investigate whether we should/can ban it after #487 and why.

When banned, it would have to be excluded from the follwing BOM entries:

[ERROR]     io.quarkiverse.cxf:quarkus-cxf:1.5.0-SNAPSHOT:jar pulls banned dependencies [org.ow2.asm:asm]
[ERROR]     io.quarkiverse.cxf:quarkus-cxf-rt-features-logging:1.5.0-SNAPSHOT:jar pulls banned dependencies [org.ow2.asm:asm]
[ERROR]     io.quarkiverse.cxf:quarkus-cxf-rt-features-metrics:1.5.0-SNAPSHOT:jar pulls banned dependencies [org.ow2.asm:asm]
[ERROR]     io.quarkiverse.cxf:quarkus-cxf-rt-transports-http-hc5:1.5.0-SNAPSHOT:jar pulls banned dependencies [org.ow2.asm:asm]
[ERROR]     org.apache.cxf:cxf-rt-ws-security:3.5.3:jar pulls banned dependencies [org.ow2.asm:asm]
[ERROR]     org.apache.cxf:cxf-rt-ws-mex:3.5.3:jar pulls banned dependencies [org.ow2.asm:asm]
[ERROR]     io.quarkiverse.cxf:quarkus-cxf-rt-ws-security:1.5.0-SNAPSHOT:jar pulls banned dependencies [org.ow2.asm:asm]

As a first step, we can do the above exclusions and check whether some tests fail.

[ppalaga]

Citing @famod from #487 (comment) :

It was excluded due to #226 (and banned in a later PR).

The runtime part of quarkus-cxf should not depend on asm.

[ppalaga]

The runtime part of quarkus-cxf should not depend on asm.

Hm... now I see. quarkus-core-deployment pulls asm via gizmo. So banning asm for both runtime and deployment artifacts is not possible. I'll try to do it for runtime modules at least.