assertrepr_compare: prefer same maxsize

[blueyed]

Previously it would say:

> assert '123456789012...901234567890A' == '1234567890123...901234567890B'"

This makes it look like the "3" might be different already.

This is clearer, and it is OK to have potentially one less char in the
right one:

> assert '123456789012...901234567890A' == '123456789012...901234567890B'"

[codecov]

Codecov Report

Merging #5731 into features will decrease coverage by <.01%.
The diff coverage is 85.71%.

@@             Coverage Diff              @@
##           features    #5731      +/-   ##
============================================
- Coverage     96.25%   96.25%   -0.01%     
============================================
  Files           117      117              
  Lines         25895    25899       +4     
  Branches       2494     2494              
============================================
+ Hits          24926    24929       +3     
- Misses          666      667       +1     
  Partials        303      303

Impacted Files	Coverage Δ
src/_pytest/assertion/util.py	95.03% <100%> (ø)	⬆️
testing/test_assertrewrite.py	85.19% <75%> (-0.06%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 300f785...cb481a3. Read the comment docs.

[nicoddemus]

We could use a trivial changelog entry I think

[blueyed]

@nicoddemus

We could use a trivial changelog entry I think

I don't think so.

But in general, what do you think about having a way to also look at commit messages when generating the changelog?
Then it could be added to the commit message when merging - without extra pushing etc.

[nicoddemus]

Not sure, we would need to see if it would be worth it