feat: add validity check

[baruchiro]

This PR is the first implementation of validity check #191.

I added the flow of validation, controlled by the --validate flag, and added validation for Github token.

[github-actions]

KICS version: v1.7.12

Category Results HIGH 0 MEDIUM 0 LOW 1 INFO 0 TRACE 0 TOTAL 1	Metric Values Files scanned 1 Files parsed 1 Files failed to scan 0 Total executed queries 49 Queries failed to execute 0 Execution time 1

[jossef]

looks good to me, I think its worth adding an optional permission scopes of the found active secrets.

regarding terminology, suggesting to use status instead of validation (active, inactive, unknown) or active (true / false)

[baruchiro]

looks good to me, I think its worth adding an optional permission scopes of the found active secrets.

regarding terminology, suggesting to use status instead of validation (active, inactive, unknown) or active (true / false)

As defined in #191, the possible values of the validation field are valid, revoked, and unknown, so it can't be a boolean field.

Since it is not guaranteed the user will enable this feature. the field might be empty, and I want its name to be meaningful and the user will understand why it is empty.

I left with the validationStatus name 😐