Forcing content view version repository regeneration does not actually regenerate some repositories
Description of problem:
The force/force_full option is not properly used on some repositories (those that use the yum_clone_distributor), and pulp takes this option into consideration for all distributors.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a content view, add a repo 'foo', publish it
2. Look at the timestamps in /var/lib/pulp/published/yum/master/yum_distributor/*CV_LABEL*ENV_LABEL*/TIMESTAMP/repodata/
3. Regenerate the repodata from the content > content views > click your view > click "regenerate repository Metadata" in the actions dropdown beside the version you just published.
metadata is not regenerated, timestamps are not updated
metadata is regenerated