LPS-44671 Introduce a new pattern for documenting any changes that break backwards compatibility for the next release

/cc @rotty3000 @juliocamarero @natecavanaugh @eduardolundgren 

As agreed in our call yesterday I have created a new pattern for documenting any breaking change going forward. Here are some decisions I made:

1. Create a directory structure instead of just adding the file at the top. I did this because it opens up the opportunity for adding more files related to the upgrade or even some tooling to facilitate it.
2. Make the file chronologically ordered. I did this so that it's much easier for developers to update it (just by adding at then end) vs trying to maintain a logical structure. After all, the biggest value of this file is to ensure that every breaking change is documented and justified. This document can later be used as the master source for release notes, upgrades instructions, etc.

If you guys have any breaking change that we have already done for 7.0, please let me know so that we add it.