Merged Monitoring and Monitoring Service into one

[DarrenDsouza7273]

• Merge monitor and monitoringService commands in cli into one

• First level implementation on skipDocker command

  • for v0.0.1 make it work with the merged monitor command to allow for opting in and out of docker setup.

• Fixes issue : Merge monitor and monitoringService commands #30

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

(#30 (comment))

[sooraj1002]

The PR is only removing monitoringService from the cli, it is not merging the functionality previously provided by it into monitoring

[sooraj1002]

The schematics should also be updated to merge monitorModule and monitor into one command like monitoring.

[DarrenDsouza7273]

@sooraj1002 Yes ill work on your reviewed suggestions and do the respective changes
also i have added draft skipDocker flag

[DarrenDsouza7273]

it even works with other Flags

[sooraj1002]

This approach is workable, but this feature should ideally be handled in combination with changes in the schematics as well since the bootstrapping is just one part of the system.

What happens when a user wants to generate monitoring related files? they would need to run two commands, nest g monitor and nest g monitorModule whereas it should ideally be implemented something as nest g monitor --skipDocker. The flag should be implemented at the level of each schematic, and while bootstrapping a new project, the --skipDocker flag should be propagated to each command

[Savio629]

Fixes/included in pr #34