Update Poetry to UV

[Jan10e]

• uv updated in workflows, pyproject and Readme; removed Manifest and setup.py
• uv lock

Checklist

Please complete this checklist before submission

• All changes were made in a separate branch. (Branches MUST have descriptive names that start with either the fix/ or feature/ prefixes. Good examples are: fix/some-bug-issue or feature/issue-templates).
• The PR commit has a descriptive commit message with a short title (first line).
• The PR targets the main branch (not dev).
• Tests for the changes have been added where applicable (for bug fixes/features).
• The documentation has been updated to reflect any changes.
• The code has been linted and formatted locally (see pre-commit-config.yaml).
• Add closes #X (where X is the issue number) in the comment to auto-close the issue that this PR fixes (if applicable).

Description template for PR

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

• Bug fix
• New feature
• Other:

What is the current behavior?

Link any open issues or pull requests here.

What is the new behavior / fix / change?

Describe the change that this PR introduces.

Does this PR introduce a breaking change for backwards compatibility?

In particular, what does the user have to consider due to this PR?

Has this PR been tested?

Please explain:

1. How has this PR been tested?
2. If tests have been added to the code base, briefly describe them.

Does this PR require an update to the documentation?

If any features have changed, or have been added, please explain how the documentation has been updated (and link to the associated PR).

Other information

Add any further details here.