feat: add and review spots

[leon-wbr]

Should follow original flow:

1. Select origin spot (if not as review)
2. Select destination spot (optional)
3. Rating, Waiting Time, Comment, Nickname (unless authenticated with Nostr)
4. Optional Fields

Afterwards, depending on authentication:

• Send the data to central server to sign with Hitchmap nsec;
• or: sign with provided credentials and post to relays.

[guaka]

to avoid the "central server" we might as well generate an nsec on the fly (and sign with that) and tell the user to store that safely in their password manager if they'd ever want to delete/edit this, or use the same identity for hitchmap in the future

later we can play with browser extensions, nsec bunkers etc, but not needed now I think
(even nip46, but it feels a bit useless because you can only sign one event at a time, nip46 could be useful for logging into a system with actual authentication like mediawiki or trustroots...)

this can still allow for a nickname, and we could later explain (or better: guide them) how to tie this to a hitchwiki mediawiki or trustroots user account

[leon-wbr]

I thought of that solution, but I thought that could frustrate users who already had accounts before. If they expect the same kind of experience as a traditional auth flow, we would have to take custody of the keys and that's something to avoid. It would be great if we could figure out a flow similar to before which doesn't make it a chore for users.

[guaka]

for "accounts"+tradflow nsecbunker may be the way

but hitchmap didn't even have any accounts not that long ago and all seemed fine

[leon-wbr]

Let's move the account discussion elsewhere. Leaning strongly towards a more custodial system which I've written a little concept for. I am however going for a traditional signer flow for now while we figure this out, so that at least we can get the functionality in for Nostr users already.

[leon-wbr]

AI slopped a little something together for us based on the standard:

Tabs seem like a good solution in my eyes, but it needs a bit more space and I like to drag on the map for selecting spots instead of whatever it did there. The simple form can also have a few more, like waiting time.

Unfortunately, getting the map + sidebar UI to work properly is a little complicated. I did it a few times and have the flow more or less figured out, I'll try to get that established.

Will clean this up, then we hunt for mistakes in it.

Would be nice to have a better validation / parsing, maybe with Zod. Would perhaps be good in processing spots, too. But I do want to be able to display the ~20-30k spots as before, however, the processing starts taking too long for my taste even on my modern Mac.

[leon-wbr]

A part of this is done, but the advanced form hasn't been adapted yet and there are some stability issues (i.e. sending events to relays can fail?). Reviewing still needs to be implemented, there are two ways, though:

1. Do not let the user specifically review a spot, but just set the location identically to it (this will cluster them together, and follow the logic that original Hitchmap wanted to eventually implement).
2. Review the spot directly by setting IDENTICAL geohash / coordinates.

Slightly leaning towards the first one, because it is a bit more organic.