Adding tests to examples

[TannerGabriel]

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
[X] Other... Please describe: Docs / Samples

What is the current behavior?

Issue Number: #1539

What is the new behavior?

Added unit and e2e test for sql-typeorm sample.

Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 4755

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 8 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.09%) to 95.194%

---

Files with Coverage Reduction	New Missed Lines	%
packages/microservices/context/rpc-context-creator.ts	4	92.23%
packages/websockets/context/ws-context-creator.ts	4	92.08%

Totals
Change from base Build 4669:	-0.09%
Covered Lines:	4358
Relevant Lines:	4578

---

💛 - Coveralls

[RodolfoSilva]

@TannerGabriel @kamilmysliwiec have any updates related to this PR?

[TannerGabriel]

Sorry, it seems that I completely forgot about this issue. My changes are now useless because the whole example changed but I could write new tests if the interest in testing the examples still exists.