GitLab

Fixes a bug where the wrong registry value names where used, so that
setting policy didn't have effect. It used a hierarchical value name
  cat1_cat2_cat3_policy
This isn't necessary since the corresponding registry key already
contains the categories:
  Software\Policies\Google\Chrome\3rdparty\extensions\<extension_id>\Policy\cat1\cat2\cat3
so that the policy is guaranteed to be unique within the key. What's
worse is that the code isn't looking for 'cat1_cat2_cat3_policy', but
just for 'policy'. Hence, the policy settings were not taken.

Bug: 900517
Test: manual
Change-Id: I2e1b83fe2ff6b0997ab22e47c986a92dcb19559e
Reviewed-on: https://chromium-review.googlesource.com/c/1356699Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Cr-Commit-Position: refs/heads/master@{#613080}