[Change Proposal] Validate/Check format_version and kibana.version correspondence on package build

## Problem

As of now package build/CI passes even if the package's `kibana.version` and `format_version` don't match.

This results in some packages having a higher `format_version` than their kibana version constraints. And thus the released package is not visible on older kibanas (even though their support is specified in the `kibana.version`).

The issue for `format_version: 3.4.0` describes this problem: https://github.com/elastic/integrations/issues/15147

## Proposal

Make the package build (and thus CI) fail if the format_version and kibana version don't correspond (meaning the package is not visible on the earliest kibana version supported by the package)

Related:
- https://github.com/elastic/integrations/issues/15147
- https://github.com/elastic/elastic-package/blob/main/docs/howto/format_version.md (doesn't yet contains info on format_version: 3.5.0 which is supported beginning kibana 9.2.0)
- before making this change proposal I created an issue in integrations repo: https://github.com/elastic/integrations/issues/15627