feat: Add options to limit generation of encode and decode methods to only specific message types

[akrennmair]

I created this PR as a possible to solution to the feature request submitted in #1084.

I added integration tests for test coverage, and updated the documentation to include the two new options.

[stephenh]

Hi @akrennmair , thanks for updating the PR! Looks like there is a build error with MessageFns...maybe we need two/separate input/output MessageFns types?

[akrennmair]

@stephenh I didn't want to touch the MessageFns type as I didn't know what it would break. What I did instead was to generate a tiny dummy encode or decode method that throws an error if the presence of the method is required.

[stephenh]

Sounds great, thanks @akrennmair !

[stephenh]

🎉 This issue has been resolved in version 2.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v2.5.0

Your semantic-release bot 📦🚀