Portal deploys now check your _redirects file before publishing

Deploys from ee-cdn-cli have checked _redirects since the file was introduced. Deploys from the portal didn’t: the file was published as it was. A mistake showed up only later, as a rule that quietly did nothing, or worse, one that did something you didn’t intend. A rule with a country condition, which we don’t support, was published without the condition and sent every visitor to the page meant for one country.

The portal now runs the same checks before it publishes:

• Errors stop the deploy. Each one names its line.
• Every problem is reported at once, up to 50, so a file brought over from another host can be fixed in one pass rather than one deploy per mistake.
• Warnings are shown but don’t stop the deploy.
• A file the CLI accepts, the portal accepts too. Both are tested against the same set of example rules as the edge itself.