[Feature Request]: Enable export/import of basic project/environment to enable easy moves between enviromments

### What would you like to happen?

Outcome:
hop-conf.sh able to export/import the basic configuration of a project and it's environments so that data and reliability engineers can have a common way of working and executing code.

Reason:
For the most part, end users create and name projects and environments manually potentially resulting in issues when deploying to other environments.
e.g. to execute a workflow using hop-run you need to supply the project and environment. it complicates execution if there is no easy way of ensuring that the project and environments match across a physical environment (Dev/Test?prod servers)

In one picture, hop-conf.sh is able to export/Import this section of hop-conf.json into a separate file that can be committed with the rest of the project.


Thank you!

### Issue Priority

Priority: 3

### Issue Component

Component: Hop Config

The request centers on hop-conf.sh and the project/environment section of hop-conf.json; first inspect how hop-conf.sh currently handles configuration and how hop-run consumes project and environment names. The work is done when that configuration can be exported to a separate, committable file and imported so projects and environments match across physical environments.

Written by the indexing model from the issue text.