feat: adding validate template type to author docs command

[AleJo2995]

Types of changes

• Hot fix (emergency fix and release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (change which affects the documentation site)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release (develop -> main)

Quality assurance (all should be covered).

• My code follows the code style of this project.
• Documentation for my change is up to date?
• My PR meets testing requirements.
• All new and existing tests passed.
• All commits are signed-off.

Summary

Closes #1464

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[AleJo2995]

This is still in draft due to pending demo. Once demo is done with current folder names, I will change them to a more generic folder and file names. e.g a folder, b folder, a, b, c file names instead of what it is now in tests

E.g tests/data/author/docs/arch-design/ssad/mock/arch-design_v1.md will be changed to be more generic

[mrgadgil]

LGTM. Thank you