Add Tool and Part Components to the Proper Files

[jmwright]

The user needs to be able to add a component to parts.yaml and tools.yaml under an abstraction that defines what the component needs to do. For instance sr create parts.wss "Infineon TLSxxx" should add a wss entry to parts.yaml with the munged description of the Infineon sensor under it.

[jmwright]

@m30-jrs I'm thinking about removing the ability to specify the name of a component as a command line argument unless a command line option (like -n/--name) is supplied, and maybe not even then. There are two main reasons for this:

1. The way we've been talking about adding lists and items, followed by the part description (which gets munged), breaks UX consistency in the app and causes confusion about what command line argument applies to what (list, item or component).
2. If users are allowed to specify names directly on the command line, it's likely to be less consistent than converting descriptions to munged IDs.

It seems like it would be better for the CLI to interrogate the user when they run sr create to get the minimum info needed to operate, and then munge descriptions into IDs. This would allow the CLI to collect the initial quantity and quantity-units too. Command line options can be supplied for automating the process of collecting that information if someone wants to wrap sliderule-cli in a script.

I think this initial interrogation process, coupled with a few extra commands to help the users change things like quantities in parts.yaml and tools.yaml would go a long way toward preventing the user from ever having to open those files.