Clean public API of components: towards more explicit delegation

[hugtalbot]

This issue is created further to #4943

This PR proposed to define base class functions as final and override these functions (which are templated) in child classes as a protected function. These changes are breaking but could be done in several steps:

1. set the function of the abstract class to final
2. fix the components which were overriding this function [FEM] Components override the template API instead of the generic one #4982
3. set the functions overriding the templated one as protected (for v25.06 ?)
4. rename functions with a clear delegate name doFunctionName() + compatibility layer
5. tests should be fixed to use the public virtual class (access protected functions)
6. add the check on the component state:
   • first check non-invalidity
   • then, check the validity

This project could have several benefits:

• cleaning the API and expliciting the delegation mechanism
• allowing to introduce and generalize more easily the componentState mechanims

[damienmarchal]

nice

[alxbilger]

If we do that, I recommend to use strong types in the functions accepting VecId. Indeed, today the VecId for a force is the same type than the VecId for a velocity, and it's a source of mistake when the function accepts both forces and velocities.