Allow dependamerger to auto-merge some PRs in the gem

[KludgeKML]

• We exclude rails, and most of the JS packages (especially govuk-frontend).

[MartinJJones]

Looks good, just a couple of thoughts/questions:

• From looking at the developer docs, do we need to update name, from Continuous integration to CI in ci.yml?

In contrast, the ci.yml must have a name property called CI, as this is relied upon by our automated tooling.

• Do we meet the Conditions required for automatic patching in the gem? for example:

"MUST only be applied where there is no manual deployment step"

[KludgeKML]

@MartinJJones Interesting!

There certainly seems to be precedent for gems: https://github.com/alphagov/govuk-dependabot-merger/blob/main/config/repos_opted_in.yml#L22C3-L22C19 ...gds-api-adapters among others are included in the list. I think I'd argue it's safe because in this case they are themselves part of apps that are manually deployed (so if government frontend auto-deploys with a broken version of this gem, although the downstream question of "which dependency in publishing components caused this" is muddied, the question of "which dependency in government-frontend cause this is clear" (ie it's publishing components). I will seek guidance.