RF: rename _() to _translate() - initial commit

- was getting a name conflict: dependency messing with global _, leading to crash back in the app

#$ find . -name '*.py' | xargs python ~/code/sub_translate.py

#import fileinput, sys, re
#for fpy in sys.argv[1:]:
#  i = 0
#  for line in fileinput.input(fpy, inplace=True):
#    sys.stdout.write(re.sub(r'\b_\(', '_translate(', line))
#    # sys.stdout is redirected to the file
RF: finishing touches (hopefully)
DOC: updated for _translate() instead of _()
Merge remote-tracking branch 'jeremy/rename-_translate-function'

Jeremy was changing the name of the translate function while I was
adding the HSV color option to builder components, sometimes on the same
line

Conflicts:
	psychopy/app/builder/components/_visual.py
	psychopy/app/builder/components/polygon.py
	psychopy/app/builder/components/settings.py
ENH: added some future-proofing to Builder view params/components

experiment.py now checks components and params as they load

Future Params in components are kept with the info but marked with:
	param.readOnly=True
They show up in dialogs greyed out and get saved to new copies of the
file untouched.

Future Components now have a class of their own (UnknownComponent) that
ensures they show up in the Builder view (again, without the user being
able to alter their parames). No code will be written for Components
from the future.
TESTS: added test for new future-proofing in f9926c8

load a file from the 'future' (with fake params and components)

Also had to rebuild the Components template as these had changed in the
futue proofing and I've renamed the generator file by @jeremygray to
make it hopefully more clear what it does ;-)
Merge pull request #688 from peircej/master

renamed _translate(), added HSV to Builder and added some future-proofing for Builder