Switch order of `createFQAN` and `createCapabilitySet` steps in `NewCapabilitySet` workflow

[shreyb]

Steve White informed me yesterday that the newest release of FERRY will add a required parameter to the createFQAN API where the capability set must be specified. This will break the NewCapabilitySet workflow as it is now.

We will need to do three things:

1. Switch the order of the createFQAN
   

   Ferry-CLI/ferry_cli/helpers/supported_workflows/NewCapabilitySet.py

   Line 223 in e1b4f40

   # 3. Create new FQAN

and createCapabilitySet

Ferry-CLI/ferry_cli/helpers/supported_workflows/NewCapabilitySet.py

Line 248 in e1b4f40

# 4. Create capability set

calls in the workflow.

2. Make sure the createFQAN call includes the newly-created capability set as a parameter.
3. Do away with the last step, "Associate capability set with FQAN", since that will be handled in (2).