Make flags / options more consistently named #6
Description
Overview
There are several flags which are formatted differently (without hyphens, e.g.), and further flags which are ambiguous as to their intended purpose.
We should evaluate the options we have and see if they are all strictly required to be presented to users, or if some could be abstracted to sane defaults with the user configuring them as overrides if they choose. A good example of this is tagless mode / altlookaside--we can just detect this and set some flags for the user without having to make it too smart. In peridot we set all these flags in the Request struct anyways, and wouldn't need to modify much if anything on that side to support these changes.
While this would be great for a user perspective, I think there may also be some benefit in this for the development of srpmproc to simplify and abstract where we can.
Recommended Next Steps
- Document purpose/behavior of existing flags/options - https://github.com/rocky-linux/srpmproc/blob/main/cmd/srpmproc/main.go#L118-L151
- Group and evaluate if some options should be organized differently; e.g., commonly used options towards the top