expression: use maximum length for integer display (#56463)

[ti-chi-bot]

This is an automated cherry-pick of #56463

What problem does this PR solve?

Issue Number: close #56462 close #45338 close #41719

Problem Summary:

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Issues related to casting integers with a non-default display width to strings have been fixed.

[codecov]

Codecov Report

Attention: Patch coverage is 77.77778% with 4 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-7.5@e62cfd5). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #56929   +/-   ##
================================================
  Coverage               ?   72.1457%           
================================================
  Files                  ?       1415           
  Lines                  ?     412785           
  Branches               ?          0           
================================================
  Hits                   ?     297807           
  Misses                 ?      94996           
  Partials               ?      19982           

Flag	Coverage Δ
unit	72.1457% <77.7777%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9400% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.5113% <0.0000%> (?)

[dveeden]

Looks like expression/issues might have issues in release-7.5 even without this PR

[lance6716]

@dveeden I think you should ask a expression package code owner https://github.com/pingcap/tidb/blob/release-7.5/OWNERS_ALIASES#L34 to triage this cherry-pick, to remove "do-not-merge/cherry-pick-not-approved" label

[dveeden]

/retest

[dveeden]

/retest

[windtalker]

lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, windtalker

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lance6716,windtalker]
• pkg/expression/OWNERS [windtalker]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-02 11:14:17.456592104 +0000 UTC m=+1067045.076246619: ☑️ agreed by lance6716.
• 2024-12-03 06:33:34.437272411 +0000 UTC m=+1136602.056926927: ☑️ agreed by windtalker.

[dveeden]

/retest