fix: the package replace logic when using tag, branch or commit

[leoporoli]

Description

Fix the package replace logic when using tag, branch or commit

The current issue is the package replace logic fails when you add a tag, branch or commit in the replace value, like this example:

replace: - github.com/kurtosis-tech/ethereum-package: github.com/kurtosis-tech/ethereum-package@da55be84861e93ce777076e545abee35ff2d51ce

If we see the evaluation error

Evaluation error: An error occurred while loading the module 'github.com/kurtosis-tech/ethereum-package@da55be84861e93ce777076e545abee35ff2d51ce/src/package_io/input_parser.star' Caused by: '/input_parser.star' doesn't exist in the package 'kurtosis-tech/ethereum-package' at [github.com/kurtosis-tech/ethereum-package@da55be84861e93ce777076e545abee35ff2d51ce/main.star:1:29]: <toplevel> at [github.com/kurtosis-tech/awesome-kurtosis/chainlink-node/main.star:2:33]: <toplevel>

we understand it's trying to import the file from this path github.com/kurtosis-tech/ethereum-package@da55be84861e93ce777076e545abee35ff2d51ce and it doesn't exist because the folder, inside the APIC file system, is created without the hash, it's github.com/kurtosis-tech/ethereum-package

This is happening because an absolute locator like this github.com/kurtosis-tech/ethereum-package/src/package_io/input_parser.star does not incorporate the concept of hash, branch or commit.

The fix is incorporated the concept of hash, branch or commit in a new AbsoluteLocator object, so this way we can specify if the absolute locator is pointing to other place than the main branch.

With this change we can accept the github.com/kurtosis-tech/ethereum-package@da55be84861e93ce777076e545abee35ff2d51ce replace value and an absolute locator string like this github.com/kurtosis-tech/ethereum-package@da55be84861e93ce777076e545abee35ff2d51ce/src/package_io/input_parser.star will be represented with an AbsoluteLocator object with locator github.com/kurtosis-tech/ethereum-package/src/package_io/input_parser.star and and tagBranchOrCommit da55be84861e93ce777076e545abee35ff2d51ce

We already had support for retrieving packages from different tag, branch or commit but only for packageId values and not for absolute locators

REMINDER: Tag Reviewers, so they get notified to review

Is this change user facing?

YES

References (if applicable)

Fix #2279

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

<sup><sub>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sub></sup>

[tedim52]

approved! Is there any chance you can provide more context on what the specific bug around locators was and what the specific fix was for it was in the PR description?

[leoporoli]

approved! Is there any chance you can provide more context on what the specific bug around locators was and what the specific fix was for it was in the PR description?

@tedim52 I added more context in the description, I hope this can put more light in the issue and the fix.

[tedim52]

Sweet, thanks for adding context to the PR, LGTM!