[#1133] Describe upgrade --force as performing the confirmed tasks, and say it does not accept the license

[vharseko]

Fixes #1133

Problem

The description of upgrade --force (INFO_UPGRADE_OPTION_FORCE_1741, shown by upgrade --help and in the generated tools reference) says that long running or critical tasks which require user confirmation "will be skipped". The code does the opposite: in non-interactive mode with --force, the confirmation callback answers YES (UpgradeCli.handle), so every task gated by confirmYN — rebuildAllIndexes, the JE / changelog / Local DB → PDB migrations — is performed. The license question is the only exception: Upgrade.checkLicence answers NO under --force, and --acceptLicense is needed.

Change

• tool.properties: the --force description now says the confirmed tasks "will be performed", and that the option does not accept the license — use --acceptLicense.
• UpgradeCli: passes OPTION_LONG_ACCEPT_LICENSE for the new %s.

The narrative in install-guide/chap-upgrade.adoc already describes the real behaviour ("also performing long running and critical tasks") and is unchanged.

Verification

Built with mvn -pl opendj-server-legacy -am compile, then ran the compiled UpgradeCli:

• upgrade --help:

  --force
      Forces a non-interactive upgrade to continue even if it requires user
      interaction. In particular, long running or critical upgrade tasks, such as
      re-indexing, which require user confirmation will be performed. This option
      does not accept the license: if the upgrade requires accepting a license,
      use the 'acceptLicense' option. This option may only be used with the
      'no-prompt' option
  

• the gendoc run (-Dorg.forgerock.opendj.gendoc=true), which produces man-upgrade.adoc for the reference, renders the same text under `--force`::.

No test is added: the change is message text only.