Add a removeCurrentItems parameter to clearOptions() to allow for either intended behavior

[dvg-p4]

• Closes clearOptions() deselects currently-selected items, but does not remove them as options #2146
• Closes clearOptions should not clear items #593 (if you call clearOptions(false, false))

• clearOptions() now, by default, removes currently-selected items in addition to deselecting them,
  as it did prior to selectize v0.12.5.
  • This behavior is controlled by a new parameter removeCurrentItems, default true.
  • If removeCurrentItems is set false, the function will instead leave currently-selected items
    available and selected, as was the case from selectize v0.12.5, until v0.13.1 introduced
    #2146 (which this change fixes).
  • For consistency, silent also has a (backwards-compatible) default value of false now.
  • Thus, the full signature is now clearOptions(silent = false, removeCurrentItems = true)

I don't feel very strongly about the new parameter being default true, as long as whatever its default value is, is correctly and comprehensively documented. You could make the argument either way.

[dvg-p4]

Let me preempt the bot marking this PR as stale by saying that it continues to be fully ready for review.

[github-actions]

This pull request is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days

[dvg-p4]

If this repo is at all being maintained, I'd personally recommend either working through the backlog of issues and PRs more frequently than your bot marks issues as stale, or turning off that functionality of your bot if you can't commit to that schedule (totally understandable, this is FOSS).

[databyte]

I try to help with maintenance but I have no way to build and release so it's seemingly harder and harder to maintain if we can't get faster releases out.

[dvg-p4]

I try to help with maintenance but I have no way to build and release so it's seemingly harder and harder to maintain if we can't get faster releases out.

no worries, I get it! let's consolidate further discussion of "is anyone actually maintaining this at all" under the ticket you just made.