Convert CLI tool to a dotnet tool

[mariomastrodicasa]

Describe the bug
The package KafkaBridgeCLI shall appears as a dotnet tool rather than a normal package.

Expected behavior
Convert the package to a dotnet tool package and give the users the ability to use the content as a console application.

Screenshots

Desktop (please complete the following information):

• OS: Any
• Version: All

Additional context
N/A

[masesdevelopers]

To create a working dotnet tool package seems mandatory to add PackAsTool option within the project. Anyway testing the resulting package it does not contains all files necessary for the runtime: only the main assemblies of the referenced packages are available, the runtime libraries of JCOBridge are missing; we tested the solutions found in NuGet/Home#4360 without success because a NuGet package hosting tools expect the files are under a folder named any under each runtime (tools\net6.0\any, tools\net5.0\any); at the end we concluded that a feasible option is to create a specific nuspec file, avoids the creation of package from project (i.e. disable option GeneratePackageOnBuild): the project is used only to create the executables.

[mariomastrodicasa]

Until now the tool needs to explicitly set the class to be used with ClassToRun command-line switch. A dotnet tool package can host more than one command: it is useful to create scripts (PowerShell, batch or sh) to execute the command directly:

KafkaBridgeCLI -ClassToRun ConsoleConsumer --bootstrap-server SERVER-ADDRESS:9093 --topic topic_name --from-beginning

becomes

ConsoleConsumer --bootstrap-server SERVER-ADDRESS:9093 --topic topic_name --from-beginning