feat(h005): support BTD download orders with service params and date range - #52

…ocalDate

Review round 1 on the BTD download support.

- Reject a partial or reversed date range in the EbicsDownloadParams constructor,
  the one place every caller passes through. A half range used to be dropped when
  the request was built, on the launcher's legacy path without even a warning; a
  reversed range is schema-valid and comes back as EBICS_NO_DOWNLOAD_DATA_AVAILABLE,
  indistinguishable from a genuinely empty period.
- Check every launcher argument before the first environment read, keystore access
  or bank call. It ran after loadUser/createUser and after --ini/--hia/--hpb, so an
  incomplete --btd order could still fire an INI request first, and INI is one-shot
  at most banks.
- Carry the report period as LocalDate instead of Date. A calendar day read out of
  an instant depends on the machine's timezone: a UTC-midnight Date becomes the
  previous day west of UTC. The Date-taking overloads are kept and now document
  that. Adds createDateRange(LocalDate, LocalDate).
- Upper-case the EBICS code list values (--service, --scope, --option, --container)
  so --container zip no longer aborts. Message names such as camt.053 stay as given.

Tests 31 -> 36. New guards were each seen failing first.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>