chore(): added alias for interface and rename alias interceptor

[Tony133]

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
• 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?

Issue Number: N/A

What is the new behavior?

Proposal:
Added alias ìtf for interface and renamed alias int in itc for interceptor

Does this PR introduce a breaking change?

• Yes
• No

Other information

[micalevisk]

and then we will need to change on nest-cli side:

• https://github.com/nestjs/nest-cli/blob/6379b32fb527730f54003df1ca1671bbeb259d4c/lib/schematics/nest.collection.ts#L58-L67
• https://github.com/nestjs/nest-cli/blob/64ddf3b4fb77200e69e15673cce1f4606a127d06/test/lib/schematics/nest.collection.spec.ts#L52-L53

[Tony133]

Right!, I created a PR for that in the Nest cli repository as well, thanks for reminding me! 👍 (see here)

[kamilmysliwiec]

Isn't it an unnecessary breaking change though? That's what worries me the most

[Tony133]

What prompted me to do this PR is that they are not very intuitive as alias names, for example interceptor is an in, while alias for the interface is not really an alias because it is the name itself. It would be nice to change them and make them more "alias" or real "alias". 😁

Anyway maybe I understand what you mean, that you would like to make them similar enough if you upgrade the nest version to a new one? But since the main version of nest v9 is on the way, there could be this change, no?