Allow Remote Agent to be started in disabled mode

It would very interesting having the ability to start up Bamboo Remote Agents and prevent them from being available until configuration is complete.

As a example:

• Company A outsources Bamboo to Company B and Company C
• Company B and Company C coincidentally have the same environment where remote agent can be run
• Company B already have remote agents up and running with Company A
• Company C issue a remote agent to Company A

What could happen:

• Builds from Company B could end up being executed in Company C before Requirement or Dedication is set