BUG: Change of behavior in casting of datetime-like types in MultiIndex
- [x] closes #43091
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit) for how to run them
- [x] whatsnew entry

Added try-except block in multi.py to reset the behaviour back to 1.2.5
Hello @shubham11941140! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:





There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2021-10-28 01:57:38 UTC Please see contributing guide for help: https://pandas.pydata.org/pandas-docs/stable/development/contributing.html > pls look at the 1.3 release. I am pretty sure we change this on purpose. datetime.date is retained which is the point here.

@jreback the change described in #43091 was caused by #38552, which was about `Index([date]).astype("category").astype(object)` round-tripping. Thanks @shubham11941140 for the PR. These changes do not appear to correspond with the changes in the PR that was identified in the issue as causing the reported change in behavior.

We also need to decide if we are reverting to 1.2.5 behavior.

I am closing for now but feel free to contribute to the discussion in #43091