Support for Gloo route_options on Canary CR

[amall015]

Describe the feature

We would like to use Flagger with Gloo route tables, however the Canary resource does not support the ability to specify route specific options (prefixRewrite, jwt/auth disabling, header manipulation, etc). This is supported by Gloo on both the virtualservice and routetable resources: https://docs.solo.io/gloo-edge/latest/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/options.proto.sk/#routeoptions

Proposed solution

Allow for the specification of these options on the Canary CR, or develop the ability for Flagger to act on route tables that have already been created.

Any alternatives you've considered?

We are unable to specify the options on the virtual service because they differ depending on the route prefix in our system.