feat(microservices): Add options param to serializer

[guiruiz]

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?

Currently the Kafka Client/Server calls the serializer passing only the packet/message value as parameter.

Issue Number: N/A

What is the new behavior?

From now the Kafka Client is calling the serializer passing the packet value and also an options object containing the pattern (topic name) as parameters.
With the optional options parameter the Serializer interface is now matching the Deserializer interface.

Does this PR introduce a breaking change?

• Yes
• No

This change doesn't introduce a breaking change because the options parameter is optional.

Other information

I'm deserializing/serializing messages using Avro Schemas with the Schema Registry, in order to do that the custom serializer needs to be aware of the topic/pattern name of each message.
Since this is an issue that other people may have I decided to contribute opening this PR.

[coveralls]

Pull Request Test Coverage Report for Build e5e1fa2b-d372-493f-9841-71d4ea30cf94

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.156%

---

Totals
Change from base Build d711baf6-cae3-43ad-bc15-20e80f939ea3:	0.0%
Covered Lines:	5720
Relevant Lines:	6075

---

💛 - Coveralls

[kamilmysliwiec]

LGTM