BUG: pd.Timedelta(big_int, unit=W) silent overflow
- [ ] closes #xxxx (Replace xxxx with the Github issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Thanks @jbrockmendel  According to the release notes of pandas 1.5.0 

> Operations with [Timestamp](https://pandas.pydata.org/docs/reference/api/pandas.Timestamp.html#pandas.Timestamp) or [Timedelta](https://pandas.pydata.org/docs/reference/api/pandas.Timedelta.html#pandas.Timedelta) that would previously raise OverflowError instead raise OutOfBoundsDatetime or OutOfBoundsTimedelta where appropriate ([GH47268](https://github.com/pandas-dev/pandas/issues/47268))

However, `pd.Timedelta(seconds=60) / 1e-9` still raises an OverflowError. Is that intended? From the changelog, it seems this should return a `OutOfBoundsTimedelta` instead.  > still raises an OverflowError. Is that intended

No.  PR to fix cases we missed would be welcome.