Circular imports if module imports are at the top of files

[lb324567]

#137 added checks to ensure the Python code conformed to best practices. However, one of the changes that should be made is to move all module level imports to the top of the file. If this is done as the code stands now, it causes circular import issues within the testing.
Part of this may be to do with the generated Fishbowl code, so this might not be something we can easily fix but it should be looked into as we should aim to have all module imports at the top of the file to adhere to best practice.

if this can be fixed, the autopep8 action should also be changed to stop the checks from skipping the E402 rule.

[t92549]

Due to how the fishbowl generated code imports work, this has to be done unfortunately:

gaffer-tools/python-shell/src/gafferpy/gaffer_operations.py

Lines 675 to 676 in 1fb1f2c

	# Import generated operation implementations from fishbowl
	from gafferpy.generated_api.operations import *