sql: add table-level max_row_size guardrails

[kaustubhbabar5]

Currently, CockroachDB only supports cluster-wide row size guardrails. However, different tables, databases may have different requirements:
Addresses #137518

sql: add table-level row size guardrails

• Introduces table-level row size guardrails that allow users to configure row size limits on a per-table basis
• This change adds two new table storage parameters:
  • max_row_size_log: Log a warning when a row exceeds this size (overrides cluster setting)
  • max_row_size_err: Return an error when a row exceeds this size (overrides cluster setting)
• SQL syntax
  • Both parameters can be
    • set via CREATE TABLE ... WITH (max_row_size_log = '10MB', max_row_size_err = '50MB');
    • altered by ALTER TABLE user_profiles SET (max_row_size_log = '10MB', max_row_size_err = '50MB');

Prioritizes guardrails in following order

1. table-level
2. cluster-level

[blathers-crl]

Thank you for contributing to CockroachDB. Please ensure you have followed the guidelines for creating a PR.

Before a member of our team reviews your PR, I have some potential action items for you:

• We notice you have more than one commit in your PR. We try break logical changes into separate commits, but commits such as "fix typo" or "address review commits" should be squashed into one commit and pushed with --force
• Please ensure your git commit message contains a release note.
• When CI has completed, please ensure no errors have appeared.

I have added a few people who may be able to assist in reviewing:

• @dikshant (author of sql/guardrails: allow table and DB level settings for SQL guardrails #137518)

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is 

[blathers-crl]

Your pull request contains more than 1000 changes. It is strongly encouraged to split big PRs into smaller chunks.

Thank you for updating your pull request.

Before a member of our team reviews your PR, I have some potential action items for you:

• We notice you have more than one commit in your PR. We try break logical changes into separate commits, but commits such as "fix typo" or "address review commits" should be squashed into one commit and pushed with --force
• Please ensure your git commit message contains a release note.
• When CI has completed, please ensure no errors have appeared.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[blathers-crl]

Thank you for updating your pull request.

Before a member of our team reviews your PR, I have some potential action items for you:

• We notice you have more than one commit in your PR. We try break logical changes into separate commits, but commits such as "fix typo" or "address review commits" should be squashed into one commit and pushed with --force
• Please ensure your git commit message contains a release note.
• When CI has completed, please ensure no errors have appeared.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[blathers-crl]

Thank you for updating your pull request.

Before a member of our team reviews your PR, I have some potential action items for you:

• We notice you have more than one commit in your PR. We try break logical changes into separate commits, but commits such as "fix typo" or "address review commits" should be squashed into one commit and pushed with --force
• Please ensure your git commit message contains a release note.
• When CI has completed, please ensure no errors have appeared.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[kaustubhbabar5]

I'll be adding database-level guardrails in separate PR. this PR is ready for review