Moving max_num_doublings of NUTS from build_kernel to kernel

[weiyaw]

Implement #564

1. Making the argument consistent with 'num_integration_steps' in HMC
2. Allows running adaptation (e.g. window_adaptation) with an arbitrary max_num_doublings

---

A few important guidelines and requirements before we can merge your PR:

• If I add a new sampler, there is an issue discussing it already;
• We should be able to understand what the PR does from its title only;
• There is a high-level description of the changes;
• There are links to all the relevant issues, discussions and PRs;
• The branch is rebased on the latest main commit;
• Commit messages follow these guidelines;
• The code respects the current naming conventions;
• Docstrings follow the numpy style guide
• pre-commit is installed and configured on your machine, and you ran it before opening the PR;
• There are tests covering the changes;
• The doc is up-to-date;
• If I add a new sampler* I added/updated related examples

Consider opening a Draft PR if your work is still in progress but you would like some feedback from other contributors.

[junpenglao]

Could you also check whether any of the code in https://github.com/blackjax-devs/sampling-book needs updating?

[codecov]

Codecov Report

Merging #566 (b6fd52b) into main (1817ee9) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #566   +/-   ##
=======================================
  Coverage   99.14%   99.14%           
=======================================
  Files          49       49           
  Lines        2099     2099           
=======================================
  Hits         2081     2081           
  Misses         18       18           

Files Changed	Coverage Δ
blackjax/mcmc/nuts.py	100.00% <100.00%> (ø)

[weiyaw]

Could you also check whether any of the code in https://github.com/blackjax-devs/sampling-book needs updating?

No update required as far as I know. But I do discover a few bugs related to the API changes from previous commits.

[junpenglao]

No update required as far as I know. But I do discover a few bugs related to the API changes from previous commits.

Thank you for double checking. If you could update those it would be much appreciated!