Add playbook input to reference an Ansible Galaxy Collection Playbook

Looking at how this is implemented right now it will always get an absolute path to the playbook
https://github.com/hashicorp/packer-plugin-ansible/blob/536562fd497fc5049018ba90db705adc6b2c9634/provisioner/ansible/provisioner.go#L812

Maybe a new input can be added to the plugin where we can use as input a playbook that exists in a Galaxy collection.
Example:
```hcl
provisioner "ansible" {
playbook = "namespace.collection.playbook"
galaxy_file = "requirements.yml"
}
```

Start in provisioner/ansible/provisioner.go at the playbook handling around line 812, and trace how the current absolute path is processed. Determine how the plugin could accept a Galaxy collection playbook alongside galaxy_file; done means the HCL example using namespace.collection.playbook and requirements.yml is supported.

Written by the indexing model from the issue text.