fix(action): forward dropped request params and fix wait_for_active_shards serialization

[marevol]

Summary

Correctness fixes to existing HTTP actions, continuing the request-parameter
serialization work from #30. Each fix was verified against the corresponding
OpenSearch Rest*Action. No new dependencies; no API changes.

Fixes

• HttpOpenIndexAction — wait_for_active_shards for ActiveShardCount.ALL
  now serializes to "all" instead of "ALL" (the server rejects the latter
  with HTTP 400). This is the same bug class fixed centrally in feat(client): add PIT, reindex/by-query, resolve-index actions and fix request-param serialization #30; this was the
  one remaining call site still using ActiveShardCount.toString(). Also forwards
  indices options.
• HttpCloseIndexAction — forwards wait_for_active_shards and indices
  options, both of which were dropped (close could otherwise return before shards
  were ready).
• HttpUpdateAction — removes the version / version_type params. The
  _update endpoint rejects internal versioning (it requires if_seq_no /
  if_primary_term, already sent), and UpdateRequest's version setters throw
  UnsupportedOperationException, so the removed block was unreachable.
• HttpIndicesAliasesAction — builds the request body from the request's own
  toXContent, so is_write_index, is_hidden, must_exist and routing are
  now emitted (a write-index alias was previously not marked as such), and a
  remove_index action no longer emits a bogus empty aliases.
• HttpRefreshAction / HttpFlushAction / HttpForceMergeAction /
  HttpDeleteIndexAction / HttpGetMappingsAction — forward indices options
  (ignore_unavailable, allow_no_indices, expand_wildcards).
• HttpForceMergeAction — also forwards primary_only.

Testing

• Adds unit tests asserting the emitted query params / body for each fix, using
  the existing ActionTestUtils offline CurlRequest inspection.
• Full unit suite: 301 tests pass (mvn test excluding the Docker /
  Testcontainers *ClientTest integration classes). The container-based
  integration tests should be run in CI to validate end-to-end.