fix: add unique id to app created page

[reneaaron]

Fixes #252

State seems to be persisted in browsers history, we fix that by using a unique URI for every app that has been created.

[im-adithya]

Nice 🙌

[im-adithya]

Did you try passing { state: null } after we go to /apps on having lastEventAt here? I can't reproduce even the actual issue

[rolznz]

It was already here, but why is there a conditional here? this seems wrong?

Also, the pairingPublicKey should be unique per app

[rolznz]

sorry, I completely misread this. I am wrong 😢

[rolznz]

but it's weird, the navigation state should work. And it seems like it's not

[rolznz]

something is wrong here (not sure what)

[rolznz]

@im-adithya @reneaaron I found how to consistently reproduce the issue:

1. Create a new app and do at least one NWC event for it
2. Delete the app
3. Create a new app

Step 3. Will lead to this bug.

The pubkey is different for each app, but SQLITE is reusing app IDs rather than properly auto-incrementing.

We fetch events by pubkey from the API, but internally we query by app ID.

And for some reason when we delete apps, the request_events are not deleted.

So this PR does actually not fix the issue, and there's nothing wrong with the routing (which passes different state each time)

[rolznz]

For some reason the foreign key on delete constraint is not working

sqlite> .schema request_events
CREATE TABLE IF NOT EXISTS "request_events" (`id` integer,`app_id` integer null,`nostr_id` text UNIQUE,`state` text,`created_at` datetime,`updated_at` datetime, method TEXT, content_data TEXT,PRIMARY KEY (`id`),CONSTRAINT `fk_request_events_app` FOREIGN KEY (`app_id`) REFERENCES `apps`(`id`) ON DELETE CASCADE);
CREATE UNIQUE INDEX `idx_request_events_nostr_id` ON `request_events`(`nostr_id`);
CREATE INDEX `idx_request_events_app_id` ON `request_events`(`app_id`);
CREATE INDEX idx_request_events_app_id_and_id ON request_events(app_id, id);
CREATE INDEX `idx_request_events_method` ON `request_events`(`method`);