feat(mix): implement lockFileMaintenance

[sheerlox]

Changes

Adds support for the lockFileMaintenance option.

Refactors the lock file detection to differentiate umbrella projects from classic ones, as this implementation won't work on the former because they share a single mix.lock file for multiple mix.exs files.

Cleans up the getPkgReleases mocks by only returning the latest version, since these tests aren't about the tool version resolution.

Context

Resulting commit: sheerlox-repros/renovate-pr-33326@7ec9c87

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

[sheerlox]

Hello 👋 Is there anything I can do to help move this PR forward? No worries if it's a time issue, I totally get it. All the best!

[sheerlox]

Could one of you please explain why we should choose of of the following over the others, from a testing point of view?

I searched for a while when I did the PR and couldn't find an answer (this is why I initially left the removeDanglingContainers mocks as I didn't know what I was working with).

GlobalConfig.set({ ...adminConfig, binarySource: 'install' });

GlobalConfig.set({
  ...adminConfig,
  binarySource: 'docker',
  dockerSidecarImage: 'ghcr.io/containerbase/sidecar',
});

iiuc we can't use toMatchObject([]) without tying the test to the implementation details of the util/exec/docker module or mocking removeDanglingContainers (as it is the first command in the exec snapshot), but is there something else I should have in mind?

[sheerlox]

sheerlox/nodelix#28

Well, that's unexpected! The update-lockfile strategy wasn't working until right now, so I'm not 100% sure what caused this PR to be raised, but I'd say it's a (positive) side effect of #33325.

[sheerlox]

Hey there 👋 is this ready for merging or can I do anything else?

[viceice]

still open conversation

[viceice]

@rarkins should we use a different log level here? i'm unsure.

[rarkins]

I don't mind too much about debug logs