Handle `interaction_range` on a sub-module level

[Luthaf]

Currently, individual sub module can request neighbor lists independently, but the end user still has to explicitly merge all NL + message passing + long range options of the component of their model to define the interaction_range manually. Instead, I think a better API would be to allow individual submodule to define their own interaction range, and then the whole model interaction range is the maximal value.

This way, a SOAP calculator can define an interaction range equal to the NL cutoff, a message passing model can define it to be n_mp_layer x cutoff, and long range models can define it to be infinite. Users assembling models from building blocks would then get the correct behavior without having to look inside the building blocks.