Add new option to toml file to exclude package is old enough

[mpgn]

Description

uv will only consider package artifacts whose upload timestamp is older than the configured cutoff. This helps avoid installing newly published package releases until they have aged for at least one day.

I also started the switch to UV without breaking any logic with poetry, both works fine but uv is just better and faster and fully compatible with pyproject.toml

Type of change

Insert an "x" inside the brackets for relevant items (do not delete options)

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Deprecation of feature or functionality
• This change requires a documentation update
• This requires a third party update (such as Impacket, Dploot, lsassy, etc)
• This PR was created with the assistance of AI (list what type of assistance, tool(s)/model(s) in the description)

Setup guide for the review

Please provide guidance on what setup is needed to test the introduced changes, such as your locally running machine Python version & OS, as well as the target(s) you tested against, including software versions.
In particular:

• Bug Fix: Please provide a short description on how to trigger the bug, to make the bug reproducable for the reviewer.
• Added Feature/Enhancement: Please specify what setup is needed in order to test the changes, such as:
  • Is additional software needed?
  • GPO changes required?
  • Specific registry settings that need to be changed?

Screenshots (if appropriate):

Screenshots are always nice to have and can give a visual representation of the change.
If appropriate, include before and after screenshot(s) to show which results are to be expected.

Checklist:

Insert an "x" inside the brackets for completed and relevant items (do not delete options)

• I have ran Ruff against my changes (poetry: poetry run ruff check ., use --fix to automatically fix what it can)
• I have added or updated the tests/e2e_commands.txt file if necessary (new modules or features are required to be added to the e2e tests)
• If reliant on changes of third party dependencies, such as Impacket, dploot, lsassy, etc, I have linked the relevant PRs in those projects
• I have linked relevant sources that describes the added technique (blog posts, documentation, etc)
• I have performed a self-review of my own code (not an AI review)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (PR here: https://github.com/Pennyw0rth/NetExec-Wiki)

[NeffIsBack]

Can you add the stuff from the poetry.toml to the pyproject.toml as well? Would be nice to have everything in there instead of heaving tons of additional files

[mpgn]

Can you add the stuff from the poetry.toml to the pyproject.toml as well? Would be nice to have everything in there instead of heaving tons of additional files

Nop, Poetry intentionally keeps local environment-specific configs out of pyproject.toml, this is why i initiate the switch to uv

[NeffIsBack]

Can you add the stuff from the poetry.toml to the pyproject.toml as well? Would be nice to have everything in there instead of heaving tons of additional files

Nop, Poetry intentionally keeps local environment-specific configs out of pyproject.toml, this is why i initiate the switch to uv

oof okay, i guess then yet another file

[mpgn]

should be good to review @NeffIsBack :)

[NeffIsBack]

LGTM

Fyi, with an update to ruff we got a lot of work... We should update all packages relatively soon and probably add python 3.14 compatibility. Gonna put that on my todo list.

[NeffIsBack]

For the future we have to keep in mind to update both the poetry as well as the uv lock file. Maybe we should even remove both to be on consistent with both tools and additionally always have the latest packages. Then we are also on the same packages as people with pipx are.