Add websocket configuration for contour ingress

[lumarel]

SUMMARY

As described in this issue, the websocket is not available through contour, as this needs special configuration.
Here is also the help page from contour.

ISSUE TYPE

• Bug, Docs Fix or other nominal change

ADDITIONAL INFORMATION

So this change basically implements a check if a contour ingress is installed on the cluster, and if yes, adds the websocket route, as well as the seperate path for that.

Unfortunately I wasn't able to spin up the tests, as it looks for be that these are broken somehow, if I can get these working somehow I will gladly run through them!
As well as, if any changes are wanted I will definitely try to improve the contribution.

[TheRealHaoLiu]

instead of adding is_ingress_contour i think we can add contour as a ingress_type and use that to trigger the setting

[lumarel]

@TheRealHaoLiu I thought about that in the first place, but refrained from that, because I thought it would be better if it autodetects the ingress controller, but yes sure I am going to rebuild the change to an upfront parameter.

One thing I'm just thinking about is in this case if it would be better, to create a dependent ingress_controller variable instead of a completely new ingress_type, as the latter one will complicate the documentation a lot more.

In case this is also not really the desired outcome, I will of course rewrite it to its seperate ingress_type and add the new type to the docs