Release notes about SectionDisplayDriver breaking changes

[Skrypt]

@Piedone

[Piedone]

Related to #15488.

[MikeAlhayek]

I thought you have added obsolete attribute to avoid this unnecessary breaking change. Having obsolete attribute to the old methods will guide users on how to upgrade without breaking their code.

[Skrypt]

From what I understood in yesterday meeting it was not necessary as it needs to be changed anyway. It will lead into needing to do the exact same change for everyone.

[MikeAlhayek]

We'll now, you'll get a compile time error and if you have a 3rd party package that depends on OC 1.x then your 3rd party library will throw an exception and prevents you from being able to upgrade until the 3rd party library offers an update too.

But if you mark the old methods obsolete, then the code will at least work as before without crashing. you can upgrade your project with no issues.

[MikeAlhayek]

I don't think we should introduce this breaking change. We should obsolete the old methods for now.