feat: add workflow to check edge case dependency updates (#2737)

[Abhishek9639]

Closes #2737

Description

Added a GitHub Actions workflow that polls external repositories weekly for dependency updates that can't be managed by Dependabot. These dependencies are documented in hardcoded-requirements.txt and have special versioning:

• pycti - checks PyPI for new releases, updates docker/Dockerfile and requirements/hardcoded-requirements.txt
• droidlysis - checks GitHub commits on master (no releases), updates pinned commit in integrations/malware_tools_analyzers/requirements/droidlysis-requirements.txt
• GoReSym - checks GitHub Releases, updates download URL in integrations/malware_tools_analyzers/Dockerfile
• box-js - checks npm registry, updates version in integrations/malware_tools_analyzers/Dockerfile

The workflow runs every Monday at 6:00 AM UTC and creates separate PRs for each dependency when updates are found.

Type of change

• New feature (non-breaking change which adds functionality).

Checklist

• I have read and understood the rules about how to Contribute to this project
• The pull request is for the branch develop
• Linters (Ruff) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.

[Abhishek9639]

Greetings @mlodic,
This is ready for review.

The workflow tracks the 4 dependencies mentioned in hardcoded-requirements.txt pycti (via PyPI), droidlysis (via GitHub commits since they don't make releases), GoReSym (via GitHub releases), and box-js (via npm). It polls weekly and opens PRs automatically when updates are found.
All CI checks are passing.

If any changes are needed, please let me know and I will make them.

Thanks

[mlodic]

can you show me the workflow results executed in our fork? that proves that this is working

[Abhishek9639]

Greetings @mlodic,
Here are the workflow results from my fork.

https://github.com/Abhishek9639/IntelOwl/actions/runs/23901798567

All 4 jobs passed successfully in 19s.
Thanks

[Abhishek9639]

Greetings @mlodic,
I have added the required proof to the PR as suggested.
Please let me know if any further changes are needed and I’ll be happy to update it.
Thanks

[mlodic]

I think you can remove the hardcoded-requirements.txt file and then yeah I can merge this.

[Abhishek9639]

Greetings @mlodic,
I've removed the hardcoded-requirements.txt file as you suggested. The PR now only contains the workflow file.
If any changes are needed, please let me know and I will make them.
Thanks

[Abhishek9639]

Greetings @mlodic,
Can you please merge this PR so that I can start working on another issue?
Thanks

[mlodic]

man, I appreciate your contribution but, again ,you are too pushy, there is no need to tag the maintainers so many times for unecessary reasons. that's absolutely not the way how members of this community should behave.

[Abhishek9639]

Thanks for the feedback, and I apologize for that. I’ll be more mindful and avoid unnecessary tagging going forward.
Thanks

[github-actions]

This pull request has been marked as stale because it has had no activity for 10 days. If you are still working on this, please provide some updates or it will be closed in 5 days.

[Abhishek9639]

Take your time no rush. Just commenting here to keep the PR active. Let me know if you need any changes.
Thanks