build!: move the GCS client into the fess-lib-gcs plugin

[marevol]

storage.type=gcs and gcs: crawling now need the fess-lib-gcs plugin:

bin/fess-setup install plugin fess-lib-gcs

Without it, the storage factory reports the missing component by name and gcs: is not a file protocol — neither fails with a missing class.

This takes 29 jars and 16.9 MiB out of WEB-INF/lib for a backend most installations never use, and stops the distribution tracking a Google SDK that releases far more often than Fess does. Nothing is left behind in core except the name the plugin registers under: StorageClientFactory has resolved clients as <storage.type>StorageClient since #3419, so fess_storage++.xml in the plugin is enough to reach GcsStorageClient, and the endpoint detection that maps storage.googleapis.com to gcs stays here.

The exclusion on fess-crawler-lasta is what actually removes the jars. fess-crawler declares google-cloud-storage at compile scope for GcsClient, which stays in that library, so dropping the direct declaration here alone would have left the whole tree in the war through the transitive path.

The dependencies that had to replace it

Three are declared because something else was living off the SDK's transitive tree:

Artifact	Who needs it
google-api-client 2.7.2	fess-ds-gsuite declares it provided and does not shade it
google-auth-library-oauth2-http 1.50.0	same
httpclient ${httpcomponents.version}	nobody here, but leaving it to the resolver hands the decision to io.rest-assured, a test dependency that brings 4.5.13 at a shallower depth than fess-crawler's request. fess-ds-sharepoint compiles against ${httpcomponents.version} with scope provided

Three more pins close version splits the replacements opened, all of the shape that left the GCS client calling a google-http-client method that did not exist (#3420):

• google-auth-library-credentials — google-api-client wins the nearest-wins tie with 1.30.0 against the 1.50.0 that the library loading it asks for.
• google-http-client-apache-v2 — the fifth member of that family, and the only one that arrives at 1.45.2.
• an exclusion of the javax flavour of the annotation API that api-common pulls.

Apart from the GCS set, three artifacts change version, each back to what its remaining consumer asks for: woodstox and stax2 to what xmlsec wants, grpc-api to what google-http-client wants.

Verification

mvn test — 7696 tests, 0 failures.

Against a built distribution with the plugin in WEB-INF/plugin, an OpenSearch 3.8.0 container and a fake-gcs-server bucket:

PASS gcsStorageClient resolves -> org.codelibs.fess.lib.gcs.GcsStorageClient
PASS StorageClientFactory returns the plugin client
PASS isAvailable -> true
PASS listObjects sees the seeded prefix -> [docs]
PASS gcs is a valid file protocol -> file:,smb:,smb1:,ftp:,s3:,gcs:
PASS a client is registered for gcs: -> org.codelibs.fess.crawler.client.gcs.GcsClient
PASS the object is fetched through the crawler client -> status=200 body=...

The last one is the point: fess-crawler's GcsClient in WEB-INF/lib fetched the object using the SDK that now lives in WEB-INF/plugin.

Without the plugin, in the same setup:

storage error : org.codelibs.fess.exception.StorageException
                No storage client is registered as gcsStorageClient for storage.type=gcs.
                Install the plugin that provides it, such as fess-lib-gcs for gcs.
gcs is a valid file protocol: false (protocols: file:,smb:,smb1:,ftp:,s3:)
crawler client for gcs:: none

Merge order

Depends on codelibs/fess-crawler#203, and stays red until that one is merged and its snapshot is published. The Run Fess step here fails on exactly the state this PR is fixing: the published fess-crawler-lasta still declares gcsClient, and Lasta Di resolves the class named by a component while it parses the Di xml, so the webapp does not start once the SDK is gone.

DiXmlParseFailureException at /components[1]/include[19]
Caused by: java.lang.NoClassDefFoundError: com/google/cloud/NoCredentials
SEVERE: Exception starting filter [lastaPrepareFilter]
SEVERE: Context [] startup failed due to previous errors

Build with Maven (the 7696 unit tests) passes; Run Fess is the only failing step and Run Integration Test is skipped after it.