Change version scheme to match Array API standard?

[mdhaber]

I thought that since the project tries to be Array API compatible (and not much more), it might be useful to match the version scheme to that used by the standard. For instance, the library is now (mostly) compatible with the standard version 2023.12, so perhaps our first "real" release would be 2023.12.0, and we'd increment that last number with bug-fix releases. Thoughts?

[seberg]

At least dask regretted calver (the 4 digit year may be worst). While the added information of the effver we all use may not matter much right now, one annoying thing about calver is that it is a one way road: there is no way back from a 4 digit year as the major version.

[lucascolley]

seems like potentially a nice idea for the future, but no need to commit to it now