dev/release: Add dev tag for proper nightly package versioning

[paleolimbot]

I forgot to put this in the release instructions, but the nightly Python packages rely on a tag to version themselves after a release:

sedona-db/ci/scripts/set_dev_version.py

Lines 60 to 62 in aa6c8ea

	maybe_last_dev_tag = git(
	"describe", "--match", "apache-sedona-db-*.dev", "--tags", "--abbrev=0"
	)

Currently this is getting calculated as 0.1.0-alpha287, which is not really the end of the world, but in theory we'd like the dev versions to have a version number greater than 0.1.0.

https://github.com/apache/sedona-db/actions/runs/17937024971/job/51004986580#step:7:20

I think creating the tag apache-sedona-db-0.2.0.dev and pushing it upstream after the version update PR merges should do it.

[paleolimbot]

@jiayuasu Can you add this tag? (I can't until I am a committer)

[jiayuasu]

@paleolimbot done. Can you check?

[paleolimbot]

Thank you! Looks good to me (on the next PR merge I'll check the version of the uploaded wheel)