revert: project-name in project_id

In https://github.com/meltano/meltano/pull/6621 we added the project name to the project_id on init. Even though we hash the id prior to sending, its addition was unnecessary and creates a few problems:

• having the project name in the id confuses the purpose of the id. We don’t need to know or include the directory name in the project id and its inclusion sends the wrong signal that we do care about it somehow
• while it’s true that project_id can be any string, we generally don’t want to encourage folks to change it unless they have a strong reason to
• when trying to correlate local testing to events we’re seeing through our production snowplow pipeline, having to hash the id is unnecessarily burdensome when we’d rather just look for the GUID itself

I would support a documentation update to make it clear that project_id can be any string but that it’s generally not recommended to update if you don’t need to.

Also, I did notice that as part of this update it seems like project_id gets put at the end of the file - is there anyway to bring that back up above the environments?

@WillDaSilva @aaronsteers

[WillDaSilva]

Thanks @edgarrmondragon. In any case, that should be handled as a separate issue from the default project ID format. @tayloramurphy

[edgarrmondragon]

is there any way to control where ProjectSettingsService.set inserts a value in meltano.yml? If not, maybe we can just edit the YAML file directly using ruamel. Since we have a guarantee that the meltano.yml file as just created, my intuition is that that would be safe enough.

@WillDaSilva it was discussed back in the ruamel PR: https://github.com/meltano/meltano/pull/6308#issuecomment-1176596663. There’s a bit of complexity involved in enforcing a position for certain keys, but it’s definitely doable.