glfw: use dependencies.build instead of deps_cpp_info

[SpaceIm]

Prefer dependencies.build instead of deps_cpp_info for the workaround related to generation of wayland-protocols pkgconf file from build context in case of 1 profile (see #21242 (comment))

/cc @uilianries

---

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[github-actions]

🤖 Beep Boop! This pull request is making changes to 'recipes/glfw//'.

👋 @Hopobcn you might be interested. 😉

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 1 (d5a9e6802a8e537a0de79903711c4e389c358dec):

• glfw/3.4:
  All packages built successfully! (All logs)

• glfw/3.3.8:
  All packages built successfully! (All logs)

• glfw/3.3.6:
  All packages built successfully! (All logs)

• glfw/3.3.7:
  All packages built successfully! (All logs)

• glfw/3.3.3:
  All packages built successfully! (All logs)

• glfw/3.3.2:
  All packages built successfully! (All logs)

• glfw/3.3.4:
  All packages built successfully! (All logs)

• glfw/3.3.5:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 1 (d5a9e6802a8e537a0de79903711c4e389c358dec):

• glfw/3.4:
  All packages built successfully! (All logs)

• glfw/3.3.8:
  All packages built successfully! (All logs)

• glfw/3.3.6:
  All packages built successfully! (All logs)

• glfw/3.3.4:
  All packages built successfully! (All logs)

• glfw/3.3.3:
  All packages built successfully! (All logs)

• glfw/3.3.2:
  All packages built successfully! (All logs)

• glfw/3.3.5:
  All packages built successfully! (All logs)

• glfw/3.3.7:
  All packages built successfully! (All logs)

[AbrilRBS]

Do you have some reported issue for these PRs, or are we expecting them to have the same issue as the original one and are preemtemply fixing it?
As far as I can see, there's no 3rd PR triggering the same case as the original PR you link, but happy to get some more insight :)