change verbose::Bool with verbosity::Int

[pasq-cat]

as discussed before in #125 .
I storngly suggest to review this pr carefully because the references to verbose were many and not all of them used in the same context.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.84%. Comparing base (37f6bda) to head (9ce642f).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #127      +/-   ##
==========================================
- Coverage   96.48%   95.84%   -0.65%     
==========================================
  Files          22       21       -1     
  Lines         655      578      -77     
==========================================
- Hits          632      554      -78     
- Misses         23       24       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pat-alt]

Thanks a lot @pasq-cat, I'll try to have a look this week (please ping me again here/Teams/our next meeting if I should forget 😅 )

[pasq-cat]

Thanks a lot @pasq-cat, I'll try to have a look this week (please ping me again here/Teams/our next meeting if I should forget 😅 )

Friendly reminder

[pat-alt]

@pasq-cat looks good to me, although I'm not really sure what's effectively changed here, i.e. isn't this the same as before with false -> 0 and true -> >0?

Maybe I'm missing something

[pasq-cat]

@pat-alt more or less. It's to avoid verbose = verbosity == 0 ? false : true in the interface. I could have just changed verbose in verbosity but once I was changing it I thought that with a direct support to integers in the future you could add multiple level of verbosity. In fact, Mlj adopts this strategy.