Import rynovate into the renovate-config-seek namespace

[AaronMoat]

• Delete all our files
• Copy all files from seek-oss/rynovate@598ee7d
• In another commit, find and replace rynovate -> renovate-config-seek

This requires workshopping, but keen for feedback and direction.

As a short summary of conversations, rynovate has evolved to be the defacto standard across SEEK and it would be good to promote that to the renovate-config-seek namespace.

There is more work to do here before widespread usage, but getting this initial diff in will help conversations

[72636c]

1. Do we intend to take over the default here? An alternative may be to reroute github>seek-oss/rynovate to a named preset like github>seek-oss/renovate-config-seek:recommended.
2. Existing renovate-config-seek consumers go via npm package, so while we don't need to reserve default, there is an open question about where we migrate them to (default, third-party-major, a separate preset that retains prior renovate-config-seek behaviour?)

[AaronMoat]

1. No strong opinions personally
2. There are very few consumers and they'll need to actively migrate away. That doesn't answer your question. I know Jahred was keen on having a preset that has similar functionality to the existing, which I'm open to doing in this PR or a follow up

[72636c]

I know Jahred was keen on having a preset that has similar functionality to the existing

I'm keen to interrogate this use case over an alternative like third-party-major. When is it acceptable for a system owner to ignore major revisions of their third-party dependencies from a tech health perspective?

[AaronMoat]

I hadn't really looked at third-party-major before but it seems like a fairly reasonable alternative to the old renovate-seek-config, to me (majors + seek package minor/patches)

[72636c]

I assume this means that we are moving from a versioned npm model (repos must explicitly upgrade to the new package version) to a GitHub default branch model (repos automatically receive merged changes). I like this change but is it contentious to anyone else?

[AaronMoat]

They're deprecated, so I hope not: https://docs.renovatebot.com/config-presets/#npm-hosted-presets

[72636c]

Reminder to change this

[AaronMoat]

Open to changing this in the PR if we can come to an agreement

[AaronMoat]

What about:

Suggested change

	* @seek-oss/indirect
	* @seek-oss/sig-backend-tooling @seek-oss/sku-maintainers

(and adjusting the admin access as per ^)

@jahredhope @72636c