Namespace connects to lazy components about hutch-python HOT 3 CLOSED

OK, I'll drop all the lazy, but I'm also taking the opportunity to minimize the number of times we recurse each device

from hutch-python.

Should we unilaterally reject all lazy devices, even those that match the class? I think it's possible to do this in a way where we minimize the getattrs but still catch the things we want.

from hutch-python.

I am kind of convinced that should avoid using any non-lazy components in our devices which we means this edge case will only exist when dealing with things like AreaDetector. If this is going to be the case I think it is fine to drop everything. Not too concerned about making groups for peoples AreaDetector plugins. If they want it they can do it explicitly.

from hutch-python.