refactor all int chainId to string

[d4mr]

PR-Codex overview

This PR focuses on changing the data type of chainId from Int to String across various models and functions, ensuring consistent handling of chainId as a string throughout the codebase.

Detailed summary

• Updated chainId to String in ContractEventLogs, ContractTransactionReceipts, and ChainIndexers models.
• Changed chainId handling to toString() in multiple queries and functions.
• Parsed chainId as Number.parseInt() where necessary.
• Modified SQL migration to alter chainId data type to TEXT.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[d4mr]

needed to wrap ${chainId} in quotes to work for a SQL string comparison. Opted to use Prisma.sql which is the recommended way of templating in SQL string.

[arcoraven]

Hm why can't this line just be:

"chainId"="${chainId.toString()}"

[d4mr]

yeah that works, and given that we know chainId is sanitised it should be fine, but just a standard best practice to not use raw string interpolation with SQL

[arcoraven]

Lets simplify it. From how I'm reading Prisma docs (source), Prisma handles the sql injection risk.

The method is implemented as a tagged template, which allows you to pass a template literal where you can easily insert your variables. In turn, Prisma Client creates prepared statements that are safe from SQL injections:

const email = 'emelie@prisma.io'
const result = await prisma.$queryRaw`SELECT * FROM User WHERE email = ${email}`