The Nativize Blueprint Assets option causes C++ collision components to ignore their extents set in a blueprint

Using the Nativize Blueprint Assets option can cause the extents of a collision component defined in code and inherited by blueprints to use its default values in a packaged build instead of the extents defined in the blueprint. This also occurs even if no extents are being explicitly defined in the constructor.

Regression?: No
This also occurred in 4.13

1. Download the attached project, generate project files, compile, and open the project
2. Ensure that the Game Default Map under Maps & Modes is set to Untitled and that Nativize Blueprint Assets is enabled under Packaging.
3. Package the project for any of the listed affected platforms and notice the shape of the UBoxComponent on the NewBlueprint in the level
4. Launch the packaged game
   Result: The extents of the box are equivalent to the values set in code instead of the ones set in the blueprint
   Expected: The extents of the box should match the values set in the blueprint

[BUG REPORT] Nativize BP breaks C++ collider component