Fix security insights naming

[thepetk]

What does this PR do?

Simply renames the SECURITY-INISIGHTS.yaml to SECURITY-INSIGHTS.yml to be alinged with the CLO Monitoring guidelines

Which issue(s) does this PR fix

fixes devfile/api#1392

PR acceptance criteria

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

• Unit/Functional tests

• Documentation

How to test changes / Special notes to the reviewer

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.16%. Comparing base (b1b0c21) to head (01639e7).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage   73.16%   73.16%           
=======================================
  Files          11       11           
  Lines        1565     1565           
=======================================
  Hits         1145     1145           
  Misses        351      351           
  Partials       69       69           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Jdubrick]

/lgtm thanks Fanis

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jdubrick, thepetk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Jdubrick,thepetk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Jdubrick]

@thepetk after that name change merge went through I noticed there is a duplicate and we have both .yml and .yaml extensions in the root of the repo.

[thepetk]

@thepetk after that name change merge went through I noticed there is a duplicate and we have both .yml and .yaml extensions in the root of the repo.

@Jdubrick Very strange, might be brought from a rebase. I've created a PR to fix the issue: https://github.com/devfile/alizer/pull/53/files