feat(manager/pip-compile): Handle isLockfileUpdate in updateArtifacts

[not7cd]

Changes

Now Upgrade objects passed as updatedDeps to updateArtifacts will be handled in command construction. Argument --upgrade-package allows for direct manipulation of pip-compile output file. This should work with updates that use range strategy update-lockfile.

Context

related to #27331, that targets unconstrained deps

Documentation (please check one with an [x])

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

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

I have verified these changes via:

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

[not7cd]

I don't know what is untested based on coverage report

Run pnpm nyc report -t ./coverage/nyc --skip-full -r text -r text-summary
---------------------------------------|---------|----------|---------|---------|-------------------
File                                   | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
---------------------------------------|---------|----------|---------|---------|-------------------
All files                              |   99.99 |      100 |   99.98 |     100 |                   
 lib/modules/manager/pip-compile       |   99.63 |      100 |   95.83 |     100 |                   
  artifacts.ts                         |   98.33 |      100 |      75 |     100 |                   
---------------------------------------|---------|----------|---------|---------|-------------------

[renovate-release]

:tada: This PR is included in version 37.199.0 :tada:

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.199.0

Your semantic-release bot :package::rocket: