rate limit: modularize the extension configuration

Currently, rate limit in envoy requires `actions` field that is defined in the virtual host and route configuration. This puts a pressure on the control plane to couple core networking configuration with the rate limit configuration (e.g. it's impossible to customize actions with ECDS). The proposal is to move actions into the extension configuration itself.