Standalone build workflow to be used by publish workflow and on new PRs & linter fixes

[DtDamianGrzes]

No description provided.

[Copilot]

Pull Request Overview

This PR refactors CI workflows into a standalone build-package workflow, updates the publish workflow to consume it, and includes minor SDK improvements.

• Add __hash__ to EndpointStatus for hashability.
• Simplify singleton creation and fix event-property iteration in extension.py.
• Extract build, test, and lint steps into a reusable build-package.yml; update publish.yml to use it.

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
dynatrace_extension/sdk/status.py	Added __hash__ method to EndpointStatus.
dynatrace_extension/sdk/extension.py	Simplified super().__new__ call and corrected loop to use value.
dynatrace_extension/sdk/communication.py	Annotated inline yaml import with # noqa: PLC0415.
.github/workflows/publish.yml	Refactored to call new reusable workflow and removed redundant steps.
.github/workflows/build-package.yml	New workflow defining build, test, lint, and packaging steps.

Comments suppressed due to low confidence (1)

.github/workflows/publish.yml:13

• The ::set-output command is deprecated in GitHub Actions. Switch to the GITHUB_OUTPUT file syntax, e.g.: echo "match=$(...)" >> "$GITHUB_OUTPUT".

        run: echo "::set-output name=match::$(echo '${{ github.ref }}' | grep -Pq '^refs/tags/v\d+\.\d+\.\d+$' && echo true || echo false)"

[maciejtokarz]

Is it needed? It is triggered in https://github.com/dynatrace-extensions/dt-extensions-python-sdk/pull/125/files#diff-c37cf2bffb2cde25cbcedc64387a46a1b752a13b0f310ecc68058b87889a3ac0R12.