policy: erase type to any

[jrobsonchase]

We're probably going to be making more changes to the schema of this. Guard against having to release new SDKs all the time whenever we do so, and defer validation to the server side.

Note: this is currently a breaking change - probably want to make it backwards-compatible.
OK, backwards-compatible now! any is better than map[string]any for this.

[jrobsonchase]

Hmmmm, this passes tests, but the Action.Config type has changed on the wire, so this won't actually work. Will need server-side support to fully support this new approach.

[TheConcierge]

hey, Josh. I like the idea here! In fact, there is an open RFC that attempts to address this exact concern of having to constantly update the SDKs. I went down the route of changing the type of the protobuf (see section in RFC), but it's difficult considering we are working with a deeply nested proto that we can't easily change the behavior of.
The idea of the RFC here is that this just becomes a string over the wire so there are no protobuf changes we need to propagate to the SDKs moving forward, everything is done server-side

[CK-Ward]

Closing this per today's discussion. @nijikokun @tammybailey