feat(platform/gitlab): handle detailed_merge_status to proceed with automerge

[javaxiss]

Changes

The behavior changed by this PR concerns only the GitLab platform. Before proceeding with automerge, a check is done on GitLab platform version and Renovate will rely on detailed_merge_status instead of merge_status attribute only if GitLab platform version is ^15.6.0.

RENOVATE_X_GITLAB_MERGE_REQUEST_DELAY environment variable is introduced to allow users define their own delay value, it is initialized to 250 by default.

Context

This PR is a follow-up to the discussion #25433. It is a version feature gate on Gitlab platform (^15.6.0) : To proceed with automerge Renovate will check detailed_merge_status instead of merge_status, which is deprecated in Gitlab 15.6

Prior to Gitlab 15.6, Renovate continues to rely on merge_status attribute.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[CLAassistant]

All committers have signed the CLA.

[viceice]

needs new tests for coverage

[viceice]

you need to fix git author and committee and then force push. otherwise we can't merge this

[javaxiss]

you need to fix git author and committee and then force push. otherwise we can't merge this

done, I have taken onboard your suggestions and remarks, as well ☺️

[viceice]

it seems you've still a wrong git author or committee, otherwise LGTM

[javaxiss]

it seems you've still a wrong git author or committee, otherwise LGTM

Sorry I committed with an account not recognized in my Github profile. It seems good now, "All committers have signed the CLA." ;-)

[renovate-release]

🎉 This PR is included in version 37.125.0 🎉

The release is available on:

• GitHub release
• 37.125.0

Your semantic-release bot 📦🚀