feat: added new generate option to control spec file name

[hrkeni]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

currently, a generated spec file always ends with .spec.ts

Issue Number: #1683

What is the new behavior?

There should be a cli flag and config option to specify the suffix to be used, with the default being spec.

nest g res foo --spec-file-suffix=test
nest-cli.json:

{
"generateOptions": {
"spec": true,
"specFileSuffix": "test"
}
}

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[kamilmysliwiec]

And how is this new option applied to schematics?

[hrkeni]

@kamilmysliwiec The changes to schematics were already made in July 22 nestjs/schematics#1077
This is just enabling CLI to use those

[kamilmysliwiec]

LGTM