[all] Deprecates the hard coded interactions in components

[damienmarchal]

Hard coding interaction in core component is not a good software design as it couple the behavior of a component and how it is used in the context of a specific interactive scene.

This PR remove this behavior and warns users. To avoid re-implementing things no one use, it is requested in the deprecation message that user need to report if they miss the feature so so we can restore it but with the proper software design.

---

By submitting this pull request, I acknowledge that
I have read, understand, and agree SOFA Developer Certificate of Origin (DCO).

---

Reviewers will merge this pull-request only if

• it builds with SUCCESS for all platforms on the CI.
• it does not generate new warnings.
• it does not generate new unit test failures.
• it does not generate new scene test failures.
• it does not break API compatibility.
• it is more than 1 week old (or has fast-merge label).

[bakpaul]

This PR is removing some usefull mechanism (VTK and LightManager). In order to pass this PR, those two component would require to provide those controller and not just say "you should code them". One solution would be to remove them from the PR before merging it.
(By the way, an issue regarding the mesh loaders and exporters will be created to be discussed and uniformised during the STC)

[damienmarchal]

Hello thank you for the feedback,

I'm strongly reluctant to hard code in c++ trivial keyboard controller because there is a lot of boilerplate code and because this also encourage software obesity by having all the application specific's user interfaces in Sofa Core, think about just changing the keypress "a" to "b" without recompiling sofa.

But I'm ok to implement that in a python controllers, does it would be ok ?

[damienmarchal]

[ci-build]

[fredroy]

[ci-build][with-all-tests]

[bakpaul]

I think that regarding the last SOFA-Dev meeting, the deprecation date is still missing. When it is added we will be able to merge it !