[PLT-0] Prep Release v.3.75.0

[adrian-chang]

Description

Release v.3.75.0

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Document change (fix typo or modifying any markdown files, code comments or anything in the examples folder only)

All Submissions

• Have you followed the guidelines in our Contributing document?
• Have you provided a description?
• Are your changes properly formatted?

[vbrodsky]

My comments are re CHANGELOG messages
I've been following the feedback previously received from MLSE (John?), which involved reviewing and polishing merge commit messages to ensure a professional look in the CHANGELOG. Additionally, I've omitted comments related to internal commits focused solely on test fixes and refactoring.
However, I'm unsure if this approach is still the preferred method. Has there been a shift towards including all commits in the CHANGELOG, regardless of their nature?
Even we stick with this approach, I think we need to fix text for a couple of those commits messages