fix(common): ParseUUIDPipe - throw exceptions with exceptionFactory only

[titivuk]

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?

ParseUUIDPipe supports exceptionFactory option. But when it validates not a string, exceptionFactory is ignored and BadRequestException is thrown from isUUID util

What is the new behavior?

isUUID util does not throw an Exception and delegates the decision to ParseUUIDPipe

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 37fe1162-b766-4cd0-9a52-bed710d01bc1

• 7 of 7 (100.0%) changed or added relevant lines in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.003%) to 94.123%

---

Files with Coverage Reduction	New Missed Lines	%
packages/common/pipes/parse-uuid.pipe.ts	1	88.57%

Totals
Change from base Build 663b9722-b143-4019-bc0c-45fba7086c7b:	-0.003%
Covered Lines:	5686
Relevant Lines:	6041

---

💛 - Coveralls

[titivuk]

We can keep original message and use exceptionFactory to throw correct exception when str is not string (not sure if it's needed). To do so we can remove the util (it's used only in the pipe) and move its code to the pipe file.
And, finally, we can add more ParseUUIDPipe tests to cover cases related to exceptionFactory usage to make sure correct exception is thrown

[titivuk]

We can keep original message and use exceptionFactory to throw correct exception when str is not string (not sure if it's needed). To do so we can remove the util (it's used only in the pipe) and move its code to the pipe file. And, finally, we can add more ParseUUIDPipe tests to cover cases related to exceptionFactory usage to make sure correct exception is thrown

Done

[jmcdo29]

LGTM