Add project name and version context to SBOM file name

[Rimsha2535]

Fixes #946

Checklist

Note: If any of the items in the checklist are not relevant to your PR, just check the box.

For any Pull Request

Is the following correct:

• the title of the Pull Request?
• the title of the corresponding issue?
• there are no other open Pull Requests for the same update/change?
• that the issue which this Pull Request fixes ("Fixes...") is mentioned?

When Changes Were Made

Did you:

• update the changelog?
• update the cookiecutter-template?
• update the implementation?
• check coverage and add tests: unit tests and, if relevant, integration tests?
• update the User Guide & other documentation?
• resolve any failing CI criteria (incl. Sonar quality gate)?

When Preparing a Release

Have you:

• thought about version number (major, minor, patch)?
• checked Exasol packages for updates and resolved open vulnerabilities, if easily possible?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ArBridgeman]

Mocking this was a good instinct, as the exasol-toolbox version will change over time. However, as the python-toolbox is used in many projects, we often do a more direct test to ensure that the 3rd party code (in this case poetry version --ansi) works as expected and is parsed in a way we expect. This way if update poetry or dependencies change that we have clearer test feedback to act upon.

[ArBridgeman]

So, I'd replace this test with:

from exasol.toolbox import __version__

def test_project_name_and_version_from_poetry():
    name, version = project_name_and_version_from_poetry(
        working_directory=PROJECT_CONFIG.root_path)

    assert name == "exasol_toolbox"
    assert version == Version.from_string(__version__)

[ArBridgeman]

💚

[ArBridgeman]

Otherwise, please add an entry for this issue in the doc/changes/unreleased.md file.