WIP: BUG: fix Timestamp.normalize with nonexistent midnight on DST change
- [ ] closes #40517
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry

Attempting an approach to fix this. Let's see if it works.

Not surprisingly, the bruteforce approach breaks a bunch of stuff, because I ended up with twice the utcoffset shift instead of once, which makes perfect sense.

What we want here instead is to get the first valid nanosecond of the day by default and normalize to that. And probably expose to the user the ability to shift back for normalization if midnight does not exist.

Will try to fix this tomorrow.
This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. closing as stale. ping when ready to continue.