Bump ffi-yajl from 2.4.0 to 2.6.0 in /omnibus (#6648)

* Bump ffi-yajl from 2.4.0 to 2.6.0 in /omnibus

Bumps [ffi-yajl](https://github.com/chef/ffi-yajl) from 2.4.0 to 2.6.0.
- [Changelog](https://github.com/chef/ffi-yajl/blob/main/CHANGELOG.md)
- [Commits](https://github.com/chef/ffi-yajl/commits/2.6.0)

---
updated-dependencies:
- dependency-name: ffi-yajl
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Remove the comments

Signed-off-by: Vasu1105 <vjagdale@progress.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Vasu1105 <vjagdale@progress.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Vasu1105 <vjagdale@progress.com>

omnibus/Gemfile

@@ -6,10 +6,7 @@ gem "artifactory"
 
 gem "ffi", ">= 1.9.14", "!= 1.13.0"
 
-# Pinning to 2.4.0 as 2.6.0 version breaks the Windows build
-# Ref: https://buildkite.com/chef/inspec-inspec-main-omnibus-release/builds/815#018a1db4-2971-4e77-8bca-32d058fe8c12/173-340
-# We can try reverting this change once it gets fixed in the omnibus-toolchain as per slack conversation
-gem "ffi-yajl", "= 2.4.0"
+gem "ffi-yajl", "2.6.0"
 
 # This development group is installed by default when you run `bundle install`,
 # but if you are using Omnibus in a CI-based infrastructure, you do not need

omnibus/Gemfile.lock

@@ -202,7 +202,7 @@ GEM
       ffi (~> 1.0)
     ffi-win32-extensions (1.0.4)
       ffi
-    ffi-yajl (2.4.0)
+    ffi-yajl (2.6.0)
       libyajl2 (>= 1.2)
     fuzzyurl (0.9.0)
     gssapi (1.3.1)
@@ -516,7 +516,7 @@ DEPENDENCIES
   artifactory
   berkshelf (>= 7.0)
   ffi (>= 1.9.14, != 1.13.0)
-  ffi-yajl (= 2.4.0)
+  ffi-yajl (= 2.6.0)
   kitchen-vagrant (>= 1.3.1)
   omnibus!
   omnibus-software!