fix: policies.yml parsing

[fabriziosestito]

Description

Due to the recent addition of policy groups, the parsing of policies.yml was broken.
This happened because of a pretty confusing serde behavior, as an attribute on an enum is renaming all the variants of the enum, not all the fields of those variants.

TODO:

• update tests

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.48%. Comparing base (631413b) to head (8b269e1).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #843      +/-   ##
==========================================
+ Coverage   61.38%   61.48%   +0.09%     
==========================================
  Files          17       17              
  Lines        1036     1036              
==========================================
+ Hits          636      637       +1     
+ Misses        400      399       -1     

Flag	Coverage Δ
integration-tests	53.91% <ø> (+0.09%)	⬆️
unit-tests	33.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jvanz]

I think this PR fixes the v1.15.0-rc1 issue we are discussing in other channels. I was testing the bug and when I applied the same change, the problem goes away. Serde was ignoring the policy mode field due the funky behavior that you linked here. To double check that, I've renamed the field to "policy_mode" in my testing policies.yml and that works as well. 🙂

[viccuad]

LGTM!