fix(api) treat bigInt as string all across the system

[mahendraHegde]

Scope

What's changed:

• remove explicit handling of bigInt on api side, treat it as string and let DB do the casting

Potential Risks / Drawbacks

• tested with PG and sqlite but not sure if any DB expect the casting as part of query binding itself
• knex doesnt parse bigInt, so the queries are sent as xxxxn to DB, hence we dont have an option but to use string

Review Notes / Questions

• found Document SQLite's lack of BigInt primary key support #20889 while working on this, as it requires some discussion i created a separate issue
• UI inputs are not handling bigInt as well, its reading the saved data well, but pasting a bigint will result in loosing the precision because of implicit conversion to number(caused by input type=number)

---

Fixes #20291

Screenshots

create

filter

invalid

[changeset-bot]

🦋 Changeset detected

Latest commit: 8ad7afe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@directus/api	Minor
directus	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[mahendraHegde]

@br41nslug ready to be reviewed

[br41nslug]

UI inputs are not handling bigInt as well, its reading the saved data well, but pasting a bigint will result in loosing the precision because of implicit conversion to number(caused by input type=number)

This is being addressed in #20287

[br41nslug]

Thanks for the great PR! Works like a charm 😄

Would only love to see that tiny constant thing addressed so we dont need a big block of comments explaining why these are hardcoded.