feat(modeldetails): removal of recommendationsPerLanguage following d…

[lprovost-coveo]

…eprecation

Removing after giving notice for 3 months

Acceptance Criteria

• My changes are publicly available, documented, and deployed in production. (i.e. on Swagger)
• JSDoc annotates each property added in the exported interfaces
• The proposed changes are covered by unit tests
• Commits containing breaking changes a properly identified as such
• README.md is adjusted to reflect the proposed changes (if relevant)
• My merge commit message will follow the commit guidelines (See Commit Guidelines)

[FelixBlaisThon]

Should this be a breaking change ?

[lprovost-coveo]

Should this be a breaking change ?
I thought about that but since the property was nullable if someone did indeed pull on this (other than ADUI * no uses there anymore) they would have a null check for the property, but I don't think anyone used this for anything, It's a bit aggressive to turn this into a major no?

[y-lakhdar]

I’m not sure how widely this property was used, but it does seem like a breaking change. Given that, I’m not convinced it should be released under a minor version bump. Would it be possible to include this in a future major release instead?

Also, I ran a search for @deprecated in the codebase and noticed several others. Perhaps we could consider grouping these deprecations and removals into a coordinated major release?