fix: update Gemfile.lock to latest bundler

[musicEnfanthen]

This PR updates the Gemfile.lock to use the latest bundler and MINGW64 environments for windows.

[craigsapp]

For my GitHub Pages website, I include the Gemfile, but exclude the Gemfile.lock file. GitHub seems to automatically generate Gemfile.lock when creating the websites, and therefore I never need to update Gemfile.lock since GitHub generates it on the fly when preparing the website.

[ahankinson]

The lock file contains the specific version used to build the site and should be checked into version control since it should be a known good build. The Gemfile itself only contains a range of versions. You really need both to ensure everyone is building on the same set of dependencies, particularly because some Ruby devs love to break things in minor and patch versions. 🤓

[craigsapp]

I have never had a problem.

[musicEnfanthen]

Thank you.

I agree with @ahankinson that, when having more than one developer contributing to a GH pages website, the .lock file is needed to ensure a controlled environment.
It may not be needed for creating and deploying the page on GH, snce GH will resolve it correctly, but when it comes to building it locally on many different developers' architectures and systems, we will more likely run into some kind of version-related conflicts sooner or later.