Fix PyPI package publishing in CI

[scholtzan]

The current setup of publishing PyPI packages via the CI is not working as the tag information is not accessible when using the path-filtering orb. This PR changes the process slightly, instead of pushing tag with new version numbers, the version number is now managed via pyproject.toml. Whenever the version number changes in that file a new package is published to PyPI (otherwise the step is skipped).

Checklist for reviewer:

• [ ] Commits should reference a bug or github issue, if relevant (if a bug is referenced, the pull request should include the bug number in the title).
• [ ] If the PR comes from a fork, trigger integration CI tests by running the Push to upstream workflow and provide the <username>:<branch> of the fork as parameter. The parameter will also show up in the logs of the manual-trigger-required-for-fork CI task together with more detailed instructions.
• [ ] If adding a new field to a query, ensure that the schema and dependent downstream schemas have been updated.
• [ ] When adding a new derived dataset, ensure that data is not available already (fully or partially) and recommend extending an existing dataset in favor of creating new ones. Data can be available in the bigquery-etl repository, looker-hub or in looker-spoke-default.

For modifications to schemas in restricted namespaces (see CODEOWNERS):

• [ ] Follow the change control procedure

┆Issue is synchronized with this Jira Task

[dataops-ci-bot]

Integration report for "Fix PyPI package publishing in CI"

sql.diff

No content detected.

[dataops-ci-bot]

Integration report for "Update .circleci/workflows.yml"

sql.diff

No content detected.