fix: populate the values.yaml for fastly ingress support

[shreddedbacon]

Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for changelog and subsystem label(s) applied

As explained in #2848 ingresses get double applied. Which for adding fastly annotations to autogenerated routes means that the changes are added, but the second apply wipes the changes out.

This adds the fastly.x values to the main values.yaml file that is consumed again later on by the secondary apply.

[tobybellwood]

LGTM - can confirm that autogen routes now get fastly if needed

    lagoon.sh/autogenerated: "true"
...
    fastly.amazee.io/service-id: newlagoon
    fastly.amazee.io/watch: "true"