fix: use the jcifs 3.x property names for NTLM parameters and SMB1 logging

[marevol]

Follow-up to codelibs/jcifs#81 / codelibs/jcifs#87, which found that jcifs 3.0.0
renamed every configuration key (dropping the .smb segment) and that old keys are
ignored without any diagnostic. Two places in this repository still use the old names.

NTLM parameters

WebAuthenticationConfig#ntlmParameters documents what a crawler config may put in
that map:

 * <li>jcifs.smb.client.SO_SNDBUF - TCP send buffer size</li>
 * <li>jcifs.smb.client.SO_RCVBUF - TCP receive buffer size</li>
 * <li>jcifs.smb.client.domain - Default domain</li>

All three are dead names.

• jcifs.smb.client.domain is a real property under its new name,
  jcifs.client.domain. The map is turned into a Properties by
  Hc5HttpClient / Hc4HttpClient and handed to Hc5JcifsEngine / JcifsEngine,
  which do new BaseContext(new PropertyConfiguration(props)). PropertyConfiguration
  looks the key up verbatim, does not find it, and uses the default — so an NTLM
  domain configured this way has been silently ignored since the jcifs 3.x upgrade.
• SO_SNDBUF and SO_RCVBUF were never jcifs property names under any prefix,
  in 2.x or 3.x. The socket buffer properties are snd_buf_size and rcv_buf_size.

The list is corrected and gains a line naming the rename, so the 2.x spelling does not
get copied back in from an old example. Once jcifs#87 ships, a configuration still
carrying the old key will also log a warning naming the replacement.

SMB1 log level

smb1/SmbClient's static block derives the jcifs LogStream level from SLF4J, but
only when the user has not pinned one:

if (Config.getInt("jcifs.smb1.util.loglevel", -1) == -1) {

Since jcifs 3.0.0 the legacy stack reads jcifs.util.loglevel — its own Config
static block does exactly that. So the guard never fires: a user who sets
-Djcifs.util.loglevel=3 has it applied by jcifs and then immediately overwritten
here. Changed to test the key jcifs actually reads.

Tests

Five test classes use these key strings as the example NTLM parameters. The keys are
opaque to the assertions — they only check the map round-trips — so this is a rename,
not a behaviour change, but leaving dead names in the tests is how the old spelling
keeps getting copied. SO_SNDBUF / SO_RCVBUF become snd_buf_size /
rcv_buf_size.

Verification

• mvn -pl fess-crawler test for the five affected classes — 94 tests, 0 failures,
  0 errors.
• mvn formatter:format && mvn license:format — no further changes.
• Property names checked against jcifs 3.0.3 (the version fess-parent pins):
  PropertyConfiguration reads jcifs.client.domain, jcifs.client.snd_buf_size
  and jcifs.client.rcv_buf_size; org.codelibs.jcifs.smb1.Config's static block
  reads jcifs.util.loglevel.