fix: fix command argument parsing in DefaultCommandDispatcher (#1924)

* Fix command argument parsing

* Fix potential resource leak by handling all possible unchecked exceptions.

* Fix test as per #1238 (comment)

* fix: resolve rebase conflicts and address review feedback

- Fix leftover conflict markers from rebase onto master
- Remove redundant parser creation in ShellBuilder — pass this.parser
  directly since DefaultCommandDispatcher handles null
- Quote script path in sourceCommand test to handle Windows backslashes

* fix: share single parser instance between dispatcher and reader

Restore the shared parser creation in ShellBuilder.build() so that
DefaultCommandDispatcher and LineReader use the same Parser instance
when none is explicitly configured.

---------

Co-authored-by: Elec332 <6115944+Elec332@users.noreply.github.com>

fix: use parser for command argument splitting (#1907)

* fix: use parser for command argument splitting (#1876)

Previously command arguments were split on whitespace, causing
quoted arguments like "part1 part2" to be parsed incorrectly.
Use Parser.parse() instead to properly handle quotes and escapes.

* fix: escape backslashes in script path for parser-based argument splitting

On Windows, the parser treats backslashes in unquoted paths as escape
characters. Quote the path and escape backslashes in the test.

---------

Co-authored-by: Elec332 <6115944+Elec332@users.noreply.github.com>

fix: add filter-by-commitish to 3.x release drafter config

Without this flag, the jline-3.x release drafter picks up PRs merged
to any branch and produces bogus draft releases with wrong version
tags (e.g. 4.1.1 instead of jline-3.x.y).

chore: fix release-drafter config for 4.x branches

- Use $NEXT_MINOR_VERSION and filter-by-commitish on master to avoid
  picking up 3.x tags
- Add release-drafter-4.0.x.yml for the maintenance branch
- Add 4.0.x branch to the release-drafter workflow

fix: status bar duplication after vertical resize (backport #1860)

Co-authored-by: Abdelilah AIT HAMOU <abdelilah.ait.hamou@oracle.com>

[maven-release-plugin] copy for tag jline-3.30.13

fix: remove proactive isNativeAccessEnabled() checks from terminal pr…

…oviders (#1846)

On JDK 24-25, Module.isNativeAccessEnabled() returns false when
--enable-native-access is not set, even though native calls still
succeed (with JVM warnings). The proactive checks in FFM, JNI, and
Exec providers caused them to reject themselves unnecessarily,
leaving only the Exec provider which cannot detect a Windows TTY,
resulting in a dumb terminal with no tab completion.

Remove the isNativeAccessEnabled() guards and let actual native calls
determine success or failure. On JDK 24-25, providers will load and
work (with JVM warnings). On future JDKs where native access is
denied by default, the actual FFM/JNI calls will throw and be caught
by TerminalBuilder.checkProvider(), which already handles provider
load failures gracefully.

[maven-release-plugin] copy for tag jline-3.30.12

fix: pass explicit version to nisse in release workflow

The 4.1.0-SNAPSHOT tag on master causes nisse to resolve the wrong
version when building from maintenance branches. Pass the tag version
explicitly to override nisse's tag resolution.

[maven-release-plugin] copy for tag jline-3.30.11