fix(react): use property mapping from component meta

[christian-bromann]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally for affected output targets
• Tests (npm test) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

When server side rendering SSR components, we currently de-camelize the property name which is a wrong assumption, given Stencil user give their properties arbitrary names, e.g. when the attribute property is used:

@Prop({ attribute: 'multi-line', reflect: true, mutable: true }) isMultiLine: boolean = false;

What is the new behavior?

The patch makes the output target pass along the mapping for attributes that Stencil then uses later when it hydrates the component.

Does this introduce a breaking change?

• Yes
• No

Other information

n/a

[tanner-reits]

LGTM