Filter unused messages

[mpkorstanje]

⚡️ What's your motivation?

Because the message stream simply writes all messages, the report is
larger than it needs to be. By filtering out step definitions, hooks and
parameter types the report becomes smaller (but not much).

Closes: #414

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

[mpkorstanje]

@davidjgoss in #414 (comment) you said:

Before implementing the specific solution suggested here I think it would make sense to strip out all messages that are not used by the html report.

Agreed. As it stands we can do without:

* `source`

* `stepDefinition`

But source is used by react components. Instead I got this set of messages as unused from Cucumber JVM (filesize workaround).

Does this make sense?

[davidjgoss]

Ah yes, source is currently used, although I am getting rid of that soon in cucumber/react-components#396.

hook is definitely used in the components to look up the name and other details of the defined hook.

But stepDefinition and parameterType can definitely be filtered out for now.

[mpkorstanje]

Okay. I'll wait for cucumber/react-components#396 then.