Templatize module and manifest files

[MAKLs]

Current Behavior

Whenever a new tool category is created, the tool belt creates tool_category.psm1 and tool_category.psd1 under pwsh-tool-belt/tool_category to prime the tool category.

However, these module and manifest files are empty, leaving the user to build them out.

Desired Behavior

Instead of priming a new tool category directory with empty module and manifest files, these files should be created from a template for ease of use.

At the very least, the tool category's manifest should be created with:

New-ModuleManifest [@manifestParams]

so that the manifest contains all of the possible fields for the user to fill.

Additionally, since module files in the tool belt should enforce the public/private exporting pattern, module files could be generated from a template and the user can edit as necessary. Possible storage locations:

• As a script file in resources in the tool belt module root
• In-line in a script file in the tool belt module's private
• In-line in the Add-ToolCategory cmdlet