Separate decide deployment

[ellie]

Description

Add a new, optional deployment for decide endpoint. If enabled, /decide will get its own deployment

Why?

Atm it looks like decide can be adversely affected by noisy neighbours. This is not what we want! It also makes debugging much easier if we can view the traffic for this independently

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

How has this been tested?

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[hazzadous]

🥳