Update Table/Column operations' signatures to be checked

[radeusgd]

Currently many of our Table/Column operations do not have checked signatures. We should update that - this will allow us to reap benefits from the type inference and will make us more prepared for testing intersection types in anger.

[enso-bot]

Radosław Waśko reports a new STANDUP for the provided date (2025-02-13):

Progress: Reviewing Table/Column signatures. It should be finished by 2025-02-18.

Next Day: Next day I will be working on the same task. Continue.

[enso-bot]

Radosław Waśko reports a new STANDUP for the provided date (2025-02-14):

Progress: Extending James's Linter tool to automate upgrading type signatures. It should be finished by 2025-02-18.

Next Day: Next day I will be working on the same task. Finish.

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2025-02-17):

Progress: Finished reformatting files and signatures, now ensuring that tests are passing. PR is ready. In the meantime got back to checking benchmarks for the error handling PR. Got a few inconclusive results - scheduled one more run, manually comparing a few stdlib ones. It should be finished by 2025-02-18.

Next Day: Next day I will be working on the same task. Compare the new benchmarks, check CI issues and try moving forward with that PR. Then next tasks.

[enso-bot]

Radosław Waśko reports a new STANDUP for yesterday (2025-02-18):

Progress: Getting the refactor PR ready, work on upadting the linter PR. Error handling PR - updated to latest develop, applied API changes diff (had to fix line endings issue on Windows) and trying to inspect a suspicious benchmark, setting up IGV. It should be finished by 2025-02-19.

Next Day: Next day I will be working on the #12316 task. Investigate possible benchmark regression; finish the changes to Linter PR.