cnspec showing failures in bool data queries as if they're assertions

[tas50]

Describe the bug
This one is a bit weird. We have some data queries in the asset inventory pack that return bool values. The CLI is showing these as assertions that have failed.

 ~/dev  cnspec scan github repo lunalectric/k8s-base --token FOO
→ loaded configuration from /Users/tsmith/.config/mondoo/mondoo.yml using source default
→ using service account credentials
→ discover related assets for 1 asset(s)
→ synchronize assets

 lunalectric/k8s-base ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────  n/a score


Asset: lunalectric/k8s-base
---------------------------

Data queries:
github.repository.owner.name: "Lunalectric"
[failed] github.repository.archived
  expected: == true
  actual:   false

github.repository.fullName: "Lunalectric/k8s-base"
[failed] github.repository.private
  expected: == true
  actual:   false

[failed] github.repository.isFork
  expected: == true
  actual:   false

asset.title: "GitHub Repository"
mondoo.version: "9.3.3"
github.repository.createdAt: 2022-10-20 17:05:37 -0700 PDT
github.repository.description: "Base K8s manifests"



Scanned 1 asset

GitHub Repository
    U lunalectric/k8s-base

[arlimus]

Yeah that's a confirmed bug! We should add a control into the compiler to let it know if we want these assessments of boolean values (in checks) or not (in regular queries).