Maintain unique identifier for launch profiles across renames

This has come up multiple times during the implementation of the new property pages/Launch Profile UI. Basically, at the Project Query API level we don't have an immutable identifier for an individual launch profile. While the launch profile _name_ uniquely identifies it within a project, the name can be changed and the UI even supports this. This ends up being treated as the removal of one launch profile and the creation of a new one which makes it difficult (impossible?) to properly maintain the selection across the rename. There may be other implications as well.

At the Project Query API level we could assign a unique, immutable identifier to each launch profile that would allow the UI to track it across remains. That would allow the UI to update the view model "in place" and avoid selection issues.

This work item tracks three separate changes:

- [ ] The addition of an "ID" to the launch profile entity in the Project Query API
- [ ] Updating the back end to populate this property, and maintain a mapping between launch profile names and IDs
- [ ] Updating the front end to make use of the ID rather than the name