Poetry-lock-package

Poetry 1.3.1 uses poetry lock version 2 which adds a files entry to the metadata in the dependencies.

This new version or poetry lock package will pick a subset of dependency attributes from the lock file, instead of using everything that is there. We might miss a field, so this is considered a minor upgrade and not a bugfix release.

Adds a build-system section to the lock package pyproject.toml.

Does not change anything for people running with `--build`, just for those who generate the project and want to inspect/move it from there.

What's Changed
* Fix the help message for --ignore argument by maresb in https://github.com/bneijt/poetry-lock-package/pull/27
* Add build system by bneijt in https://github.com/bneijt/poetry-lock-package/pull/29

New Contributors
* maresb made their first contribution in https://github.com/bneijt/poetry-lock-package/pull/27

**Full Changelog**: https://github.com/bneijt/poetry-lock-package/compare/0.4.4...0.4.5

This release closes issue 24 where some attributes where copied to the lock package project that should not be.

The generation of the lock project approach has changed to only include some attributes instead of deleting unwanted attributes.

This is a behavior change, if you miss any attributes in the generated package, please open a Github issue.

If the project requires a package A and package B and package B only requires package A with a marker, then the lock package should not require A with a marker as B suggests, but A directory without applying markers requested from B for package A.

Closes 20

This is a bugfix to fix matching the lock package name to the project package name, when the project package name has been added using a different form (adding `pybluez` instead of `PyBluez`)