7.5.0 broke coverage-badge

[ErwinJunge]

Describe the bug
The recent release of 7.5.0 broke our usage of coverage-badge

To Reproduce

1. What version of Python are you using? 3.12
2. What version of coverage.py shows the problem? 7.5.0
3. What versions of what packages do you have installed? coverage-7.5.0 coverage-badge-1.1.0
4. What code shows the problem? dbrgn/coverage-badge@db8de11
5. What commands should we run to reproduce the problem?

# first, run pytest with coverage enabled
python3 -m pip install coverage-badge # this pulls in coverage
coverage-badge -o badge.svg
Traceback (most recent call last):
  File "/usr/local/bin/coverage-badge", line 8, in <module>
    sys.exit(main())
             ^^^^^^

  File "/usr/local/lib/python3.12/site-packages/coverage_badge/__main__.py", line 171, in main
    total = get_total()
            ^^^^^^^^^^^

  File "/usr/local/lib/python3.12/site-packages/coverage_badge/__main__.py", line 76, in get_total
    return coverage.results.Numbers(precision=cov.config.precision).display_covered(total)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Numbers' object has no attribute 'display_covered'

Expected behavior
Command generates coverage badge

Additional context
Issue likely caused by dropping of method in 4e50273#diff-9ecbfd6fa815c19afb2ab33c252cab155422453c975ed61f671617eb95ef840eL230

[ErwinJunge]

This issue is potentially invalid, since coverage-badge updated to match coverage 7.5.0 in dbrgn/coverage-badge#28.

My remaining question is now just whether the dropping of Numbers.display_covered was intentional, or accidental. If it was intentional, this issue is definitely invalid and can be closed.

[nedbat]

The dropping was intentional, a refactoring of an internal interface. I'm happy to talk to people who need other supported interfaces.