Add surf_batch_size to Boozer transform to control memory usage

[dpanici]

• Add surf_batch_size as a kwarg to the Boozer transform compute variables to allow control of memory usage when using with large number of surfaces
• Added as a plumb-thru kwarg to
  • QuasisymmetryBoozer and Omnigenity objectives
  • make_boozmn_output utility function

Especially helpful when making high res boozmn.nc using DESC

[github-actions]

Memory benchmark result

|               Test Name                |      %Δ      |    Master (MB)     |      PR (MB)       |    Δ (MB)    |    Time PR (s)     |  Time Master (s)   |
| -------------------------------------- | ------------ | ------------------ | ------------------ | ------------ | ------------------ | ------------------ |
  test_objective_jac_w7x                 |    0.43 %    |     4.114e+03      |     4.132e+03      |    17.86     |       31.64        |       30.55        |
  test_proximal_jac_w7x_with_eq_update   |    0.79 %    |     6.560e+03      |     6.612e+03      |    51.80     |       155.88       |       156.73       |
  test_proximal_freeb_jac                |   -0.35 %    |     1.336e+04      |     1.331e+04      |    -46.42    |       82.03        |       80.95        |
  test_proximal_freeb_jac_blocked        |   -1.14 %    |     7.718e+03      |     7.630e+03      |    -87.93    |       69.50        |       70.48        |
  test_proximal_freeb_jac_batched        |    0.01 %    |     7.630e+03      |     7.631e+03      |     0.82     |       70.40        |       69.69        |
  test_proximal_jac_ripple               |   -0.55 %    |     3.545e+03      |     3.526e+03      |    -19.49    |       55.56        |       55.16        |
  test_proximal_jac_ripple_bounce1d      |   -1.87 %    |     3.807e+03      |     3.736e+03      |    -71.08    |       69.83        |       69.43        |
  test_eq_solve                          |    1.61 %    |     1.910e+03      |     1.941e+03      |    30.67     |       58.29        |       58.88        |

For the memory plots, go to the summary of Memory Benchmarks workflow and download the artifact.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.32%. Comparing base (0e502bd) to head (1d44157).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2267      +/-   ##
==========================================
- Coverage   94.32%   94.32%   -0.01%     
==========================================
  Files         101      101              
  Lines       28866    28870       +4     
==========================================
+ Hits        27229    27232       +3     
- Misses       1637     1638       +1     

Files with missing lines	Coverage Δ
desc/compute/_omnigenity.py	99.60% <100.00%> (+<0.01%)	⬆️
desc/objectives/_omnigenity.py	97.04% <100.00%> (+0.02%)	⬆️
desc/vmec_utils.py	90.78% <100.00%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

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

[ddudt]

Looks fine, but has it been tested? Like running a test with multiple surfaces, and using this to only compute a few surfaces at a time.