Fix parsing some YAMLs due to outdated libyaml

[deivid-rodriguez]

While working on PNPM, I was going crazy because Dependabot could not parse the following YAML file:

https://github.com/ice-lab/icestark/blob/ec2d44244a2b4ebd7af0e0ff0a10f528b33b8a64/pnpm-lock.yaml

However, it would be parsed just fine on my dev machine.

On my dev machine:

$ ruby -rpsych -e 'Psych.load_file("tmp/ice-lab/icestark/pnpm-lock.yaml")'
# ok

On the development container:

$ ruby -rpsych -e 'Psych.load_file("tmp/ice-lab/icestark/pnpm-lock.yaml")'
/usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:455:in `parse': (tmp/ice-lab/icestark/pnpm-lock.yaml): did not find expected ',' or '}' while parsing a flow mapping at line 1308 column 17 (Psych::SyntaxError)
	from /usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:455:in `parse_stream'
	from /usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:399:in `parse'
	from /usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:323:in `safe_load'
	from /usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:369:in `load'
	from /usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:671:in `block in load_file'
	from /usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:670:in `open'
	from /usr/local/lib/ruby/gems/3.1.0/gems/psych-4.0.4/lib/psych.rb:670:in `load_file'
	from -e:1:in `<main>'

After investigating, turns out I was using a newer version of libyaml locally, which must've corrected some bugs.

Unfortunately, updating the underlying libyaml is painful, but I think it can be done, so this is my take at it.

An alternative approach would be to avoid parsing YAML. For my purposes is doable, since I just wanted to detect the version used by the PNPM lockfile and that can be figured out pretty reliably without parsing YAML. But I was worried that this could be biting us in other places so I'm trying to upgrade libyaml.

[brrygrdn]

This upgrade makes sense to me!

Regarding the test failures, the Updater spec failure looks like we might have a new flake potentially introduced by #7075 - it's worth rebasing/merging main to see if it clears up just in case but we might need to go look at that.

[deivid-rodriguez]

I hope it will be good after #7113 🤞.

[deivid-rodriguez]

Well, that didn't do the trick. Hopefully it's fine after #7114.

[jeffwidman]

Seems fine to me.

It looks like Focal (which we're on now) and Jammy (which we'll be moving to in #5030) both pull in 0.2.2 but starting in Kinetic (22.10) libyaml-dev defaults to 0.2.5: https://packages.ubuntu.com/search?suite=default&section=all&arch=any&keywords=libyaml-dev&searchon=names

[jeffwidman]

Should this change happen regardless of the libyaml bump? Or does somehow nuking the entire ~/.bundle dir help with docker image caching more than nuking ~/.bundle/cache?

[deivid-rodriguez]

It's because I need to configure Bundler globally to use the downloaded sources and the previous rm -rf ~/.bundle would wipe out the configuration, which is also needed when installing gems from omnibus/.