fix #4793 Updating schema definition so it doesnot show "repository" key required in "galaxy.yml"

[rivv0]

fix : Updated the galaxy.json schema used by ansible-lint to remove the repository key from the list of required properties for galaxy.yml. According to the [Collection Galaxy metadata structure], the repository key is optional and should not trigger a schema violation.
Fixes issue #4793 - ansible-lint raised a schema[galaxy] error with very high severity if repository was missing from galaxy.yml, even though it is not required by the official schema. This caused confusion for users and blocked further linting, especially in VS Code with the Ansible extension.
##Changes
->ansible-lint will no longer fail with a schema error when repository is missing from galaxy.yml.
->Developers will receive a warning (if the new rule is enabled) rather than a blocking error.
->Improves compatibility with the official Ansible Galaxy metadata specification and the VS Code Ansible extension.

[github-actions]

Label error. Requires exactly 1 of: breaking, build, chore, ci, docs, feat, fix, perf, refactor, style, test. Found: . Follow https://www.conventionalcommits.org to get auto-labeling to work correctly.