Fix wrong mapped meta tags for the client and via version

[TheMeinerLP]

Proposed changes

This PR fixes some small isues with 1.21.4 client and via version.

Fixes ViaVersion/ViaVersion#4241

Types of changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

• I have read the CONTRIBUTING.md
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

Since 1.21.3 the client checks very persicily which tags are send and which are not.

In some cases the upstream forgot the tags or mapped wrong for the client. Also we found out, Velocity don't display such errors in the console only in the log, but that behavior can maybe only our problem because our "Cloud"-Solution.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[theEvilReaper]

LGTM