v1.16: keep console v1.24

[daipom]

Which issue(s) this PR fixes:

• Fixes 'console' gem v1.25 causes LoadError #4487 for v1.16 branch

What this PR does / why we need it:
console gem v1.25 causes LoadError because it has changed some namepaths (#4487).
v1.25 has been supported on the master branch at #4492, but on v1.16, we should keep v1.24 to prioritize stability.

Docs Changes:
Not needed.

Release Note:
Not needed since there is no specification change.

[daipom]

I am concerned about how CI fails...

• https://github.com/fluent/fluentd/actions/runs/9189163333/job/25270604120?pr=4500

[daipom]

I am concerned about how CI fails...

* https://github.com/fluent/fluentd/actions/runs/9189163333/job/25270604120?pr=4500

Sorry, I missed that environments using Ruby 2 had been using the console gem version 1.19.0.
We need to fix the dependency condition.

[daipom]

It seems < 1.25.0 would be the correct condition for us.

[daipom]

I have confirmed failing tests are about

• Backport(v1.16): Fix a failed test of ConsoleAdapter (#4477) #4489

So, merging this and #4489 will resolve the current CI issue for v1.16.

On the other hand, I came up with a another solution to keep console < v1.24.0 (not < v1.25.0).
Then, we don't even need #4489.

[daipom]

On the other hand, I came up with a another solution to keep console < v1.24.0

I'm going to check if it has anything to do with vulnerability.

[daipom]

On the other hand, I came up with a another solution to keep console < v1.24.0

I'm going to check if it has anything to do with vulnerability.

I have confirmed this has nothing to do with vulnerability.
Using bundler-audit, I have confirmed that keeping the console < v1.24 does not increase vulnerability of dependencies both in Ruby 3 and Ruby 2.

Let's keep console < v1.24 in the v1.16 branch.

[daipom]

Let's keep console < v1.24 in the v1.16 branch.

I have made a PR for this:

• v1.16: keep console v1.23 #4510