uPortal pins springVersion=4.3.30.RELEASE explicitly, but resource-server
1.5.x transitively depends on Spring 5.x. Without an exclusion, a build
bumping resource-server to 1.5.x ends up with both Spring versions on
the classpath and javac resolves org.springframework.web.util.UriUtils
against the Spring 5 API — where encodePathSegment(String, String) no
longer declares 'throws UnsupportedEncodingException'. The catch clause
in uPortal-utils-core's Util.encodePathSegment() then becomes unreachable
and compilation fails with:

  Util.java:143: error: exception UnsupportedEncodingException is never
  thrown in body of corresponding try statement

This is exactly the CI failure on #2537 (Renovate's resource-server
1.3.1 → 1.5.2 bump), and the fix originates from @Naenyn's #2915 where
this exclusion is part of a larger 193-file PR. Landing it independently
on master unblocks #2537 and any other branch bumping resource-server,
without coupling to the Bootstrap/jQuery work in #2915.

Exclusion policy mirrors what #2915 applies:
  - resource-server-api:  exclude spring-jcl (module-level) and all slf4j
  - resource-server-utils: exclude all of org.springframework and all slf4j

The narrower exclusion on resource-server-api reflects that it's a
smaller artifact; the broader exclusion on resource-server-utils
prevents the full Spring 5 web stack from riding along.

Verified locally:
  - master + this change (resourceServerVersion=1.3.1):
    :uPortal-utils:uPortal-utils-core:compileJava BUILD SUCCESSFUL
  - master + this change + resourceServerVersion=1.5.2 (simulated):
    :uPortal-utils:uPortal-utils-core:compileJava BUILD SUCCESSFUL
    (the Util.java error goes away)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>