Method to 'lock' plugins in a project and update existing lock files

So that we can fully move off of discovery.yml, we should add a method to lock all plugins.

@aaronsteers from your last comment on the GitLab issue, will you create a relevant “lock all” issue? I’m not seeing one in https://github.com/meltano/meltano/issues?q=is%3Aissue+is%3Aopen+lock

Proposed spec details:

• https://github.com/meltano/meltano/issues/5961#issuecomment-1145378980

_Originally posted by @tayloramurphy in https://github.com/meltano/meltano/issues/5925#issuecomment-1141520551_

[aaronsteers]

Agreed with @edgarrmondragon. - I don’t feel very strongly either - but we should try to have consistent practices.

I think my preference would be --all but in certain contexts --all is optional when otherwise implied, and would likely be the default behavior if nothing different is requested.

If we went this direction, basically all of these to be equivalent ways to say ‘all’:

meltano discover
meltano discover --all
meltano discover all      # already exists
meltano install
meltano install --all
meltano lock
meltano lock --all
meltano job list
meltano job list --all
meltano test -all
meltano test <plugin_name>
meltano test <plugin_name> --all

Also related: ‘interactive’ #3153 .

When there’s really no other way to run the command besides --all, we likely would leave it off. meltano job list is a good example of where there’s no other way to run this. But in future, if we have a --filter option, then --all would make more sense. Again, it likely is the default behavior but it could improve readability if there’s any confusion.

[edgarrmondragon]

@aaronsteers Yup, that looks good