 DOC: updated documentation for BusinessHour and BusinessDay
This PR is related to PR #50182.
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).

Updated documentation for `BusinessDay`, `BusinessHour`, `CustomBusinessHour`. Corrected lists of parameters and provided more examples.
Could you, please, @MarcoGorelli, review my PR?

> Thanks for working on this @natmokval ! Got some minor comments, but overall this is a nice improvement

Thank you @MarcoGorelli, I like doing it. I find the idea of slightly improving the documentation of offsets reasonable.

Agreed, I did copy-and-paste this example from CustomBusinessHour. The PR is updated as you suggested. > Almost there 💪
> 
> There's some CI failures from the docstring validation script, check https://github.com/pandas-dev/pandas/actions/runs/3707564825/jobs/6284132896

Thank you MarcoGorelli, for your help. I checked the errors raised by the docstring validation script in CI and fixed them. It's interesting, why if I run the docstring validation script locally these errors don't occur.
 > I checked the errors raised by the docstring validation script in CI and fixed them. It's interesting, why if I run the docstring validation script locally these errors don't occur.

My guess is that you hadn't re-compiled your C extensions (`python setup.py build_ext`) - you'll need to do that any time you modify `.pyx` files (as you did here, or as can happen when you fetch and merge upstream/main) Thank you MarcoGorelli, for your comment. Usually, I run `python setup.py build_ext -j 1 `, `python -m pip install -e . --no-build-isolation --no-use-pep517`and smth like `python scripts/validate_docstrings.py pandas.offsets.BusinessDay` after modifying  .pyx files. Otherwise, html won’ be rebuilt.
Probably this time I missed something.

On the other hand, when I tried to reproduce my mistake, I run `python setup.py build_ext -j 1 --force`, and then 
the docstring validation script raised my error. Maybe it would be better to use `--force` while re-compiling the C extensions.
 if you just do `python setup.py build_ext`, then only the files that have changed since you last compiled will be recompiled, whereas `--force` recompiles everything - usually the first one's fine (it's what I usually do), but occasionally things go wrong and I have to use `--force`. hopefully the meson build will make this work a lot better - there's a PR open for that, don't know how far away it is from being ready though