Vendor wheel package for offline fixture

[thitch97]

Summary

Updates vendored packages for offline fixture. Resolves #240

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[thitch97]

Vendoring the missing package from the errors seen in #240 solved the issue but I haven't quite ascertained what changed to cause the failures. I noticed, however, that in #142 the same thing was done for setuptools which gives me a bit of confidence as far as precedent. I haven't had time yet to look into it and the answer may be simple but I wonder why either of those two need to be vendored at all given we bundle them with pip.

[robdimsdale]

I haven't had time yet to look into it and the answer may be simple but I wonder why either of those two need to be vendored at all given we bundle them with pip.

That's my concern too. wheel is bundled with the pip dependency, so why do we need to vendor it again?

[thitch97]

@robdimsdale Perhaps we get this change in and create an issue to investigate the need to re-vendor wheel and setuptools? My preliminary investigation didn't point me to anything but I'd be willing to dig into it further.

[robdimsdale]

Sure. It's probably time for us to dig in a bit deeper to the topic of vendoring wheel, setuptools, etc, but I agree that we should unblock the pipelines.