Update CI to include 3.15

[Erotemic]

Some overdue CI improvements. May also look into removing setup.py entirely.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.40%. Comparing base (0c932ab) to head (0ae50a4).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #446      +/-   ##
==========================================
- Coverage   85.12%   81.40%   -3.73%     
==========================================
  Files          21       21              
  Lines        2413     2484      +71     
  Branches      376      410      +34     
==========================================
- Hits         2054     2022      -32     
- Misses        259      347      +88     
- Partials      100      115      +15     

Files with missing lines	Coverage Δ
line_profiler/autoprofile/autoprofile.py	90.90% <100.00%> (ø)
line_profiler/cli_utils.py	89.79% <100.00%> (-0.11%)	⬇️
line_profiler/line_profiler_utils.py	85.71% <100.00%> (-10.34%)	⬇️
line_profiler/scoping_policy.py	94.44% <100.00%> (-3.23%)	⬇️

... and 7 files with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Erotemic]

@Theelx @TTsangSC

I should probably cut a release to get 3.15 wheels out. Is there anything either of you want to land first? Or any reason I shouldn't cut a new release?

[Theelx]

@Erotemic Would you be releasing a new bugfix version, minor version, or major version? If a minor version of major version then I'd like to get some speedups in (I'm putting some final polishing on the next speedup PR now), but a new bugfix version would be totally fine by me.

[Theelx]

Oh also: the speedups PR doesn't keep support for 3.8 and 3.9 since they've been EOL for nearly a year now, and 3.10 went EOL 2 weeks ago. It only supports 3.10 through 3.15 (which ends up having some benefits in code readability and maintainability, as well as speed). So, that'll have to be a major version bump when they're all in.

[TTsangSC]

#442 and #431 will probably take a while, and we have decided before to punt #440 until after that has landed, so no blockers on my end.

@Theelx it's probably alright that your new code drops 3.9 because IIRC that has already been done further up the main branch.

[Erotemic]

@Theelx I've historically been a bit loose on distinguishing patch and minor. I'm was planning to do the next release as 5.0.3, but maybe because it drops 3.8 and 3.9 I should do a minor version. I suppose now that I'm thinking about it I'll bump to 5.1.0.

We can include your speedups in a 5.2.0, as I'd like to give myself time to review and understand, but also get 3.15 wheels out there.

[Theelx]

Ah ok, that sounds good! In my PR at #447 I assumed that the speedups would be in 5.0.4, but I can update it to have a 5.2.0 entry once 5.1.0 is released.