premature invoice deletion: fix interval in sql template

[huumn]

fixes #1485

It looks like prisma's interpretation of intervals in templates changed at some point. I didn't find anywhere else where we use intervals this way.

QA: 6. made invoices, reproduced bug, then made some more invoices, ran job - no deletions, made one of the invoices artificially old, ran job - only old one deleted.

[ekzyis]

Also reproduced the bug. Makes sense that this syntax confuses Prisma. I also tested it with this query:

await models.$queryRaw`
SELECT id, created_at
FROM "Withdrawl"
WHERE now() > created_at + interval '${'1 year'}'`

It fetched withdrawals that were clearly too young. Using Prisma.sql didn't explain how Prisma interprets this though:

console.log(Prisma.sql`
SELECT id, created_at
FROM "Withdrawl"
WHERE now() > created_at + interval '${'1 year'}'
AND hash = '${'how does this look in Prisma.sql?'}'`.sql)

SELECT id, created_at
FROM "Withdrawl"
WHERE now() > created_at + interval '?'
AND hash = '?'

On a sidenote, I think we should also delete preimages since we delete payment hashes but they can be derived from the preimage or only delete bolt11s.

I think the question why we not only delete bolt11s came up before. The reason was that payment hashes are sensitive because they can be used for correlation iirc.

Following that reasoning, we should then also delete preimages.

[huumn]

true we weren't storing the preimages in all cases before