fix: add support for nested maven properties

[yeikel]

What are you trying to accomplish?

Updates our maven parsing logic to allow parsing from more complex builds such as the ones that use nested properties

Fixes #13713
Fixes #13988
Fixes #13236

How will you know you've accomplished your goal?

Using the image from main, this is the output we can expect as documented in #13713

Reproducer: https://github.com/yeikel/dependabot-issue-13713

dependabot update -f job.json
... some logs omited for brevity
updater | +----------------------------------------------------------------------------------------------+
updater | | Errors |
updater | +---------------------------------+------------------------------------------------------------+
updater | | Type | Details |
updater | +---------------------------------+------------------------------------------------------------+
updater | | dependency_file_not_evaluatable | { |
updater | | | "message": "ERROR: Invalid expression: /project/.${grpc" |
updater | | | } |
updater | +---------------------------------+------------------------------------------------------------+

After this change:

proxy | 2025/12/10 00:44:05 [049] 200 http://host.docker.internal:58225/update_jobs/cli/create_pull_request
{"data":{"base-commit-sha":"2743e98a2a25267ae9bfdab9a4c756625c50e439"},"type":"mark_as_processed"}
proxy | 2025/12/10 00:44:05 [050] PATCH http://host.docker.internal:58225/update_jobs/cli/mark_as_processed
proxy | 2025/12/10 00:44:05 [050] 200 http://host.docker.internal:58225/update_jobs/cli/mark_as_processed
updater | 2025/12/10 00:44:05 INFO Finished job processing
updater | 2025/12/10 00:44:05 INFO Results:
updater | +--------------------------------------------------------+
updater | | Changes to Dependabot Pull Requests |
updater | +---------+----------------------------------------------+
updater | | created | io.grpc:grpc-netty ( from 1.76.2 to 1.77.0 ) |
updater | +---------+----------------------------------------------+
proxy | 2025/12/10 00:44:06 Skipping sending metrics because api endpoint is empty
proxy | 2025/12/10 00:44:06 5/23 calls cached (21%)

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[yeikel]

@kbukum1 Please note that I updated the body because this change also fixes #13236 as well as one more scenario that @rhusar pointed out

[kbukum1]

@kbukum1 Please note that I updated the body because this change also fixes #13236 as well as one more scenario that @rhusar pointed out

Thanks @yeikel, I will try to find sometime this week or maybe next week to review it. It seems to be fixing a few issues. So I need sometime to review it.

[yeikel]

@kbukum1 Please note that I updated the body because this change also fixes #13236 as well as one more scenario that @rhusar pointed out

Thanks @yeikel, I will try to find sometime this week or maybe next week to review it. It seems to be fixing a few issues. So I need sometime to review it.

@kbukum1 Could you please take a look and let me know if you have any additional question, feedback or any scenario I should cover? Thanks as always for your time