Occasional Bluesky Responses with non-tag-URI ids

[snarfed]

Hey @JoelOtter, we settled on tag:bsky.app,2013:... key ids for Bluesky Responses, right? That's happening correctly most of the time, but we're occasionally using raw at:// URIs as Response key ids instead. There are 50 of them in the datastore so far. Example: at://did:plc:fdme4gb7mu7zrie7peay7tst/app.bsky.feed.post/3jt2hqcbvod2a

This looks like the cause of @laril's failures here: https://brid.gy/bluesky/did:plc:mzvszw2oinlhjryugr5kluyp?responses_after=2023-11-07T14:06:23.826459+00:00

[snarfed]

These are still happening, two for https://brid.gy/bluesky/did:plc:atsrwbmgqyeko5cjtzt5cymo on 11/9 and four for https://brid.gy/bluesky/did:plc:7dzg2vnr65pvlqgb2ziqgm4d on 11/12. I suspect discover (ie Resend for post) is the culprit.

[snarfed]

These are still happening, 114 total now.

[snarfed]

Still happening, slowly. 124 total now. @StarrWulfe reported this recently on one of his responses: log, Response entity.

[snarfed]

Still happening occasionally, most recent is 10/4.