UX around installed release name and namespace

[hasheddan]

trafficstars

Currently we force users to either be upgrading from a helm release named crossplane or universal-crossplane. Though it is not a frequent occurrence, users are not required to actually helm install Crossplane or UXP with those names. This means that as up currently functions, users could not interact with installs that use alternate names. A simple solution for this case would be to support a --name flag for all UXP commands. However, this makes our installer abstraction somewhat leaky in that a release is a helm concept. In practice, any other installer we build may also need to support "names" for installs as well, and would likely want to support upgrading a helm installed Crossplane, so it may not pose much of an issue. In the worst case, the name flag would be ignored by other installer backends. If the --name flag had a UXP_NAME env var counterpart, dealing with alternatively named installs may not be too cumbersome, but there has also been some discussion around storing UXP install information in ~/.up/config.json.