Some interfaces introduce parameters and attributes to many objects without enforcing their effect

[GiudGiud]

Bug Description

TransientInterface introduces the implicit parameter and the _implicit attribute, which is implemented properly in Kernel.C and affects Coupleable.C and nowhere else afaik. Users and app developers do not know about it, and generally wont use it properly because the logic is confusing (it swaps out current and old, and old and older in coupleable discretely)
so for example: _is_implicit ? coupledValue("u") : coupledValueOld("u") is wrong. Because in the back-end, coupleable does return (_c_is_implicit) ? var->sln() : var->slnOld();
This interface is used by 90% of objects in MOOSE

MaterialPropertyInterface introduces use_interpolated_state and prop_getter_suffix which are only used in objects that actually retrieve material property (stateful ones for the latter). This is not all of the user objects, most of them carry the parameter with no benefit.

SetupInterface introduces execute_on to numerous objects, some of which do not implement timestepSetup or execute() and therefore do not change their execution behavior

Steps to Reproduce

Examine TransientInterface
or
set implicit = true in a finite volume kernel and watch nothing happen differently

Impact

Avoid frustration from using parameters which are not respected

We need to enforce the respect of user parameters by design

[Optional] Diagnostics

No response

[GiudGiud]

I ll update the issue at some point. My initial assessment wasn't quite right