john might have screwed up ace3p-extensions lfs history

1. Commit caa3fec0 changed .gitattributes to assign all contents in the data subdirectory to lfs. At the time, there was an existing file jobs.json in there that was not committed to lfs.

2. Cloning the repo now fails in CI (fedora), for example, https://open.cdash.org/test/598446558, because the jobs.json file exists in both git and git-lfs spaces. (For some reason, this was not detected on developer machines - Ubuntu and Windows.)

3. The jobs.json file is no longer used and can be removed, but I think we have to update history to remove it before commit caa3fec0.

4. As a project maintainer, I think I can unprotect the master branch and force-push to master, but would sure like to get some input from the smarter developers before taking such a drastic step (and messing with every developer who has pulled from master in the past 24 hours....)

@ben.boeckel @ryan.krattiger1 can we discuss today? maybe at or just after CMB Core meeting.