Add empty_requirements to collection_remote

[saito-hideki]

What does this PR do?

Add new empty_requirements parameter to the collection_remote module clear requirements.yml contents.

How should this be tested?

  tasks:
  - galaxy.galaxy.collection_remote:
      ah_host: "galaxy.example.com"
      ah_username: "<YOUR_ADMIN_USERNAME>"
      ah_password: "<YOUR_PASSWORD>"
      name: "example-remote"
      empty_requirements: true
      sync_dependencies: true
      validate_certs: false
      state: present

Is there a relevant Issue open for this?

• Fixes Unable to remove requirements.yml from a remote. #413

Other Relevant info, PRs, etc

• None

[djdanielsson]

I am not sure if I like this, I think we might just need to tweak the code (role and/or python) to accept "" and thus remove any requirements that are currently in the remote. Thoughts @sean-m-sullivan @Tompage1994

[Tompage1994]

My gut feeling is that this isn't a good way to do this. Ideally we should just be able to set requirements: [] and it work. I'm intreaged as to why this doesn't work and how it does actually work through the API

[Tompage1994]

My gut feeling is that this isn't a good way to do this. Ideally we should just be able to set requirements: [] and it work. I'm intreaged as to why this doesn't work and how it does actually work through the API

I've found a better way to do this where this bug is simply fixed. I'm going to close this PR, but thanks for the contribution @saito-hideki