constant-update-2018 changed coverage for constant fields #38284
Description
When we switched to constant-update-2018 we started performing constant evaluation in the front-end. This means that VM no longer performs constant evaluation and as a result we don't mark various static const fields as executed in coverage.
Given that front-end would evaluate all constants in the dill I think it is fair to mark all static const fields as executed in coverage.