Setting a plan as disabled prevents specs of publishing its configuration

Issue Summary

The enable plan configuration should not prevent a plan to be published. This is not a coherent/intuitive behavior. Enabling a plan and publishing it are different things which will create confusion for users.

Steps to Reproduce

1. Create a specs plan configuration in Bitbucket with the plan configuration disabled:

...
 public Plan plan() { final Plan plan = new Plan(new Project()
 .key(new BambooKey("SPECS"))
 .name("specs project"),
 "Specs Plan",
  new BambooKey("PLAN"))
 .enabled(false)
... 

1. Configure a spec linked repository in Bamboo with the expected permissions
2. Run the specs scan 

Expected Results

1. The plan is created
2. The plan has the master branch disabled

Actual Results

1. The plan is not published

Note

This behavior is not coherent. If we publish a specs plan and later set the plan as disabled through specs it will be still available in Bamboo. In other words, disabling a plan should not prevent it to be published.

Workaround

1. Create the plan enabled
2. Disabled the master branch through specs