fix: update YARAify URL in FREE_TO_USE_ANALYZERS playbook

[YadavAkhileshh]

Description

This PR updates the YARAify download URL in the FREE_TO_USE_ANALYZERS playbook configuration to use the new yarahub endpoint as announced by abuse.ch.

Fixes #3140

Changes made:

• Updated YARAify URL from the deprecated API endpoint to the new yarahub endpoint
• Created a new migration to apply this configuration update
• Included reverse migration for rollback capability

This ensures users can continue downloading the latest YARA rules from YARAify without interruption.

Type of change

• Bug fix (non-breaking change which fixes an issue).

Checklist

• I have read and understood the rules about how to Contribute to this project
• The pull request is for the branch develop
• A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
  • I strictly followed the documentation "How to create a Plugin"
  • Usage file was updated.
  • Advanced-Usage was updated.
  • I have dumped the configuration from Django Admin using the dumpplugin command and added it in the project as a data migration.
  • If a File analyzer was added and it supports a mimetype which is not already supported, you added a sample of that type inside the archive test_files.zip.
  • If you created a new analyzer and it is free, please add it in the FREE_TO_USE_ANALYZERS playbook.
  • Check if it could make sense to add that analyzer/connector to other freely available playbooks.
  • I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
  • If the plugin interacts with an external service, I have created an attribute called precisely url.
  • If the plugin requires mocked testing, _monkeypatch() was used in its class.
  • I have added that raw JSON sample to the MockUpResponse of the _monkeypatch() method.
  • I have created the corresponding DataModel for the new analyzer.
• I have inserted the copyright banner at the start of the file
• Please avoid adding new libraries as requirements whenever it is possible.
• If external libraries/packages with restrictive licenses were added, they were added in the Legal Notice section.
• Linters (Black, Flake, Isort) gave 0 errors.
• I have added tests for the feature/bug I solved (see tests folder).
• If the GUI has been modified:
  • I have provided a screenshot of the result in the PR.
  • I have created new frontend tests for the new component or updated existing ones.
• After you had submitted the PR, if DeepSource, Django Doctors or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.

[mlodic]

please check deepsource failures, that suggest to optimize this code.

[mlodic]

also, instead of a lot of if, you can just use .get() and have fewer lines

[mlodic]

please provide a screenshot of the plugin section showing the correct data in the GUI