Add linter to enforce import rules

[DominicOram]

In mx-bluesky we have enforced some import rules with a linter DiamondLightSource/mx-bluesky#568. We could do the same with dodal. The rules will probably be at least:

• common doesn't import from devices
• devices.ixx doesn't import from devices.iyy

Acceptance Criteria

• We implement rules discussed on this issue
• Accompanying docs are written if the rules are not clear

[callumforrester]

How about "nothing within dodal imports from beamlines, excluding tests"? beamlines is essentially just configuration and I don't think anything should depend on it.

[DiamondJoseph]

Having just stumbled into making a circular dependency: love it.

[rtuck99]

Also plans can depend on devices but not the other way around

[stan-dot]

How about "nothing within dodal imports from beamlines, excluding tests"? beamlines is essentially just configuration and I don't think anything should depend on it.

what if we make 'beamlines' just YAML? 👀

[callumforrester]

That possibility was discussed at the bluesky workshop at NOBUGS. I think if we went that route we would be trying to find a multi-facility solution for loading devices. Currently everyone has rolled their own using either databases, config files, or code-as-config (like dodal).

[DominicOram]

Given the feedback on this I think we can say that it's been agreed upon that we do it. Updating acceptance criteria and pulling into next hyperion sprint