Explore the usage of the template via pipx

[jorgepiloto]

💡 Feature request

At the moment, users are forced to install cookiecutter to be able to bake their projects. This ships with the following disadvantages as pointed out by @asbfall:

• Users need to know the url of this repository in order to run cookiecutter gh:pyansys/pyansys-template. If at some point this repo URL is changed, users should be aware of it. Otherwise, previous command will fail.
• Users require from installing cookiecutter in a venv. Although not mandatory, this is a good practice. Users might not be familiar with this workflow. This is the reason behind pipx.

🎯 Goal

The main goal of this feature request is to substitute the current workflow:

cookiecutter gh:pyansys/pyansys-template

by:

pipx run pyansys-template

One additional advantage are, for example, is the ability to pass arguments and options. Imagine having multiple templates and users being able to select which one of those to be baked (or even the build-system):

pipx run pyansys-template --template pylib --build-system poetry
pipx run pyansys-template --template gRCP

[jorgepiloto]

After merging #8, this project ships now as a Python package with an entry point named ansys-templates. This can be installed with pipx. Let us close this issue and focus in #10.