release-1.9: set VERSION to 1.9.3-dev

[KristofferC]

No description provided.

[DilumAluthge]

To provide some context for others, we discussed this on Slack, and the purpose of this is so that people that are using e.g. 1.9-nightly in their GitHub Actions CI can see a version number (e.g. 1.9.3-DEV) that more accurately depicts what they are running.

Before this PR, someone running 1.9-nightly would just see e.g. 1.9.2 as the version number (during the period of time after 1.9.2 was tagged and before 1.9.3 was tagged), and this leads to confusion, because the user wonders whether they are actually using the correct nightly.

[ararslan]

Historically we've used the suffix pre to denote the version between patch releases. I'm not sure that really makes sense though because, for example, v"1.9.3-pre" > v"1.9.3-alpha"; so if we were to have alpha or beta versions for a patch, they'd be considered earlier than a "pre." That's actually why we use scream case on master: v"1.9.3-DEV" < v"1.9.3-alpha", as one would want. Seems like we should follow suit here?

[KristofferC]

That makes sense to me.