Regression: Rugged Gem does not support pruning like shellgit provider

The current rugged gem code in r10k does not support pruning the repos, meaning any customer that uses a significant amount of feature branches overtime will cause the local r10k cache to bloat and take up all disk space. This happens as temporary branches , such as feature branches which are normally deleted from the upstream repo, have objects that are pruned overtime in the shellgit provider. In the field , this took 6 weeks at a larger deployment so I think this issue needs to be addressed right away.
On the open source side, I can tell you that only a small number of people were using rugged as I did not add support for even setting git providers in the zack/r10k module until almost a year after rugged support was added to r10k and not a single pull request came in.

This code was never added to the rugged gem, but as rugged is now the default in Code manager , this issue needs to be addresses as its a major regression in longterm stability for anyone using code manager vs zack/r10k and the webhook