Accept --location option

[ahangarha]

This PR add a -l, --location option to the project, which can be used in the following commands:

• apply-template
• ps
• run
• run:detached

Question: Should we have CPLN_LOCATION as well? --> Added in ad26c1e
Question: Should we add an option to prevent override by env variable? (like org and app)

---

Closes #100

[rafaelgomesxyz]

Just one small thing, but need to change it in multiple places.

[ahangarha]

Known issue:

Passing non-exisiting location causes error:

➜  cpl ps --location aws-eu-central-1
rails-7975c5cb68-vftmk
redis-5d9554cd95-czj9b
postgres-0

➜  cpl ps --location aws-us-east-1   
- message: >-
    /org/mostafa-demo/gvc/tutorial-app/workload/rails/deployment/aws-us-east-1
    does not exist
  id: b31c6c3d-3b4c-4277-b73d-1e13cf17817a
  status: 404

[rafaelgomesxyz]

Let's also add Justin's comment from https://github.com/shakacode/heroku-to-control-plane/pull/92/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R172 here, since this PR is adding the option.

[ahangarha]

@rafaelgomesxyz Should we check with the ControlPlane actual deployment to ensure the location we use matches the location of the deployed project?

I guess there should be multiple edge cases. We may need to discuss or address those situations in later PRs.

What do you think?

---

Notice: This PR's implementation may be affected by #110 implementation.

[rafaelgomesxyz]

@rafaelgomesxyz Should we check with the ControlPlane actual deployment to ensure the location we use matches the location of the deployed project?

Maybe in another PR, I don't think it fits into the scope of this PR.

[rafaelgomesxyz]

Some minor changes.