Ensure consistent percentage formatting across FE and pulses

[markbastian]

Dashboard rendering of percent columns and the html export produced when emailing a pulse do not use the same number of significant digits. In the example below, the dashboard shows 2 digits after the decimal point and the pulse html rounds to the nearest integer.

To reproduce:

• Create a model and edit the user metadata on a column with values in the range of [0, 100] as :type/Percentage.
• Create a question based on that model.
• Add both items to a dashboard.
• Email the dashboard.
• View the email body.

You should see the values represented with different precision.

The following animation demonstrates the problem behavior.

The unit test metabase.pulse.pulse-integration-test/result-metadata-preservation-in-html-static-viz-test is a good basis to set up a unit test for this behavior.

AC:

• A unit test that computes both the in-app rendered value and the and the exported HTML value.
• These values should be the same.
• If the in-app values are determined on the FE, perhaps manually set the expected values to what is on the FE.

[markbastian]

Fixed by #36431