Revisit the `gluster-ansible-features` requirement to perform CTDB tasks

[anoopcs9]

I would prefer to not add unnecessary artifacts to main tasks because of specific backends needs.
Could we consider using gluster ansible collections just to install gluster itself but keep ctdb and
samba installation separated ?

Originally posted by @xhernandez in #13 (comment)

That's something we thought of during early stages and somehow didn't pursue it further. May be its
time? With few additional tasks added to common YAML I think we can completely avoid the dependency
on gluster-ansible-features collection. Are you planning to come up with such a change(of course in a
separate PR)?

Originally posted by @anoopcs9 in #13 (comment)