build(ci): Remove staticmajor due to false positives

[alpe]

Description

The current staticmajor version reports a false positive with cli/export.go with the resleak analyzer.
I have also tried some older versions but same or other problems occur.
As this was the only analyser active, I remove the action for now.

Example for a manual execution:

docker run -it --platform linux/x86_64 --entrypoint=sh -v=.:/src ghcr.io/orijtech/staticmajor_action@sha256:29e54e92ebf08a9bca219c03ce996c0f461cf52d01af20216d40b458e6c7339e
# cd /src ; /staticmajor -resleak -test=false ./...

False positives make it hard to trust the CI and create extra work for devs not familiar with the history of the project.

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage