text: Title: replace Expect.Equal(someBoolean, ...)
  Body: ### What would you like to be added?
  
  The `test/e2e` tests are full of assertions which compare a boolean against true or false, often without any additional explanation. When those assertions fail, the error message is useless for understanding what went wrong, basically just saying "expected false to be true".
  
  All of those assertions should be replace with `if (<failure check>) framework.Failf(<informative message>)`.
  
  Such locations can be found by grepping:
  ```
  $ git grep 'Expect.*Equal([^,]*, *\(true\|false\)' | wc -l
  272
  ```
  
  Example:
  ```
  test/e2e/storage/vsphere/vsphere_volume_diskformat.go:  framework.ExpectEqual(isAttached, true)
  =>
  if (!isAttached) {
     framework.Failf("volume %s is not attached", ...)
  }
  ```
  
  Some other places compare values. Those should be replaced with a comparison assertion. Example:
  ```
  test/e2e/upgrades/apps/etcd.go: framework.ExpectEqual(ratio > 0.75, true)
  =>
  gomega.Expect(ratio).To(gomega.BeNumerically(">", 0.75), "ratio too small")
  ```
  
  It makes sense to split this work into individual PRs, one per OWNERS file under test/e2e. Here's a list of directories:
  - [ ] test/e2e/apimachinery
  - [ ] test/e2e/apps
  - [ ] test/e2e/auth
  - [ ] test/e2e/autoscaling: https://github.com/kubernetes/kubernetes/pull/106200
  - [x] test/e2e/cloud/gcp
  - [x] test/e2e/cloud
  - [x] test/e2e/common/network
  - [ ] test/e2e/common/node
  - [ ] test/e2e/common/storage: @Ahmed-Aghadi
  - [x] test/e2e/framework: https://github.com/kubernetes/kubernetes/pull/105939
  - [x] test/e2e/framework/providers/vsphere
  - [x] test/e2e/framework/volume
  - [x] test/e2e/instrumentation/logging
  - [ ] test/e2e/instrumentation: https://github.com/kubernetes/kubernetes/pull/106233
  - [x] test/e2e/kubectl
  - [x] test/e2e/lifecycle
  - [ ] test/e2e/network/netpol @Ahmed-Aghadi
  - [ ] test/e2e/network @Ahmed-Aghadi
  - [ ] test/e2e/node: https://github.com/kubernetes/kubernetes/pull/106486
  - [ ] test/e2e/scheduling: https://github.com/kubernetes/kubernetes/pull/106486
  - [ ] test/e2e/storage: https://github.com/kubernetes/kubernetes/pull/105860
  - [x] test/e2e/testing-manifests/storage-csi
  - [ ] test/e2e/upgrades/apps: https://github.com/kubernetes/kubernetes/pull/105774
  - [ ] test/e2e/windows: https://github.com/kubernetes/kubernetes/pull/106220
  
  When creating a PR, use `<directory>: enhance assertions` as title. Use one commit per PR, squash when addressing feedback. Unless noted otherwise, @chetak123 will work on PRs. Help may be welcome.
  
  /sig testing
  /help
  
  ### Why is this needed?
  
  Better output for developers when tests fail.
  