Add missing parameters to broken sites

[marcosholgado]

https://app.asana.com/0/0/1203012116406182/f

This PR adds the missing parameters for autoconsent and urlParameterRemoved to the broken sites test

[GuiltyDolphin]

@marcosholgado I think we want to update the README too, with:

• urlParametersRemoved - boolean - if URL parameters were removed
• consentManaged - boolean - if a cookie popup was handled on the page
• consentOptoutFailed - boolean - if the opt-out process failed
• consentSelftestFailed - boolean - if the rule's self-test failed

[marcosholgado]

@marcosholgado I think we want to update the README too, with:

• urlParametersRemoved - boolean - if URL parameters were removed
• consentManaged - boolean - if a cookie popup was handled on the page
• consentOptoutFailed - boolean - if the opt-out process failed
• consentSelftestFailed - boolean - if the rule's self-test failed

Yup! Done

[GuiltyDolphin]

Okay this LGMT unless we:

1. want to include the params in the expectReportURLParams field (cc @kdzwinel)
2. want to add any tests where these params are going to be set to 1

[kdzwinel]

Yeah, now that we have those new params we should add some tests that actually use them. This can be a follow up PR though.

[kdzwinel]

Readme says that those were meant to be booleans?

[marcosholgado]

Fair point :D Actually it depends on how you define a boolean, is it true/false or 1/0 or is it the same thing? The reporting failed because we were using true/false and the expectation was 1/0 so I guess is not really a boolean but a value of 1 or 0.

I think 1/0 is confusing though and we are using booleans in other places (i.e. true/false for wasUpgraded) so I find it weird that these few parameters need 1/0.