Encode additional coordinates in url

[philippotto]

I adapted the CSV format in the url hash so, that key=value pairs can be added to the end of the hash.

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• open a 4d dataset (e.g., https://rememberadditionalcoordinates.webknossos.xyz/datasets/sample_organization/idr0101A-4d/view)
• move through it
• check that the url hash contains something like #0,0,0,1,1.3,0,0,180,additionalCoordinate-t=123

Issues:

• fixes Preserve view position along ND axes on page reload #7271

---

(Please delete unneeded items, merge only when none are left open)

• Updated changelog

[philippotto]

@normanrz What do you think about the encoding? If we want to go for brevity, we could change
additionalCoordinate-t=123 to aC-t=123 in the URL.

[normanrz]

@normanrz What do you think about the encoding? If we want to go for brevity, we could change
additionalCoordinate-t=123 to aC-t=123 in the URL.

I like the key=value encoding. Concise and extendable. We should've done that from the start :D
I'd prefer a shorter key, such as pos-t or aC-t.

[philippotto]

@normanrz bump 🧋