fix(misconf): do not use semver for parsing tf module versions

[nikpivkin]

Description

Terraform does not use semantic module versioning, so we must use the github.com/aquasecurity/go-version/pkg/version package to parsing module versions.

Related issues

• Close bug(misconf) Terraform module: "Failed to load module "improper constraint:" #6537

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[nikpivkin]

@simar7 I haven't noticed any problems with the github.com/aquasecurity/go-version/pkg/version package. Or should we use the github.com/hashicorp/go-version package to handle module versions like terraform does?

[knqyf263]

I implemented github.com/aquasecurity/go-version based on github.com/hashicorp/go-version with more support on specifiers (a.k.a version range). Version parsing should work in the same way.