For some time, certain headers have been restricted to "document" headers.
This has always been a bit confusing, especially for people that didn't want this behaviour (e.g. see #133). With the work in #173, #174, and #185, we can allow users to choose how to customise the policies that are applied. e.g. we can have endpoint-specific policies, or we can customise on a per-request basis. Consequently, it makes sense to remove this niche functionality in favour of policy selector.
As part of that, need to expose the configured policies in the policy selector context.
For some time, certain headers have been restricted to "document" headers.
This has always been a bit confusing, especially for people that didn't want this behaviour (e.g. see #133). With the work in #173, #174, and #185, we can allow users to choose how to customise the policies that are applied. e.g. we can have endpoint-specific policies, or we can customise on a per-request basis. Consequently, it makes sense to remove this niche functionality in favour of policy selector.
As part of that, need to expose the configured policies in the policy selector context.