Added a provider to manage yum repos the right way :)

I think we totally got it wrong the first time! Just deleting the file,
does not actually delete the repo correclty as it leaves the yum cache
unchanged.

So when I thought about how to solve that, I suddenly thought we should
just use the provider to rollback/delete/remove instead of just
managing the files. So this works very nicely and does exactly what one
would expect.

The strange/dangerous thing here is that I didn’t add a depend on the
yum cookbook. But I did that on purpose… I assume that if you want to
zap your obsolete repos, you need to define the once you want first so
the yum cookbook already is loaded for that.

I’ll see if I can add a check so it just gives some debug output is
it’s not actually there.
With this additional coe, you do not have to make the zap cookbook depend on yum

This way (for future reference also) the zap cookbook can remain very
light without a whole list of dependencies, but at the same time do the
things you expect when the decencies are there
Added an option to call zap inline at a certain point in your run

This is needed for example when you clean out yum repos… As long as the
obsolete yum repos are still there ad somewhere along the line (in the
same run) you need a package from a new repo, it will fail because the
old (unavailable one) is still there. Now with the option immediately
you can call the zap action right where you need it, if it is important
for the remainder of your run.
Much cleaner solution as in this case the logic stays in this file
Merge pull request #8 from svanharmelen/run_immediately

Added an option to call zap inline at a certain point in your run
Added some documentation to match the changes...
Merge pull request #7 from svanharmelen/add_yum_repos

Add yum repos