add end-to-end test that generating a new blueprint produces no diff?

[davepacheco]

I believe that on a freshly-installed system, if you generate a new blueprint, it should contain no differences from the current (initial) target blueprint. We should have a test that verifies this. I think this would have to go into the end-to-end suite and not the live test suite since the live test suite can't assume it's running on a freshly-installed system.

I'm hopeful this would have caught #7299.