chore(workflows): add skywalking-eyes license header check

[homksei]

Description

Added skywalking-eyes license header check:

• .github/workflows/skywalking-eyes.yml workflow (actually, the check itself)
• .github/.licenserc.yaml config for checker

---

Additionally:

Copyrights in some files were updated:

• Added license header to the following .md files:

  • .github/ISSUE_TEMPLATE/RFC.md
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/documentation.md
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/pull_request_template.md
  • CODE_OF_CONDUCT.md

• Removed second year in copyright notice for the following files:

  • cpp/daal/src/externals/service_math_ref.h
  • cpp/oneapi/dal/algo/decision_forest/backend/gpu/train_kernel_hist_impl.hpp
  • cpp/oneapi/dal/algo/decision_forest/backend/gpu/train_kernel_hist_impl_dpc.cpp
  • cpp/oneapi/dal/algo/decision_forest/backend/gpu/train_service_kernels.hpp
  • cpp/oneapi/dal/algo/decision_forest/backend/gpu/train_service_kernels_dpc.cpp

• Fixed framing for the following .rst files (in docs/source):

  • docs/source/404.rst
  • docs/source/api/algorithms/clustering/dbscan.rst
  • docs/source/api/algorithms/clustering/index.rst
  • docs/source/api/algorithms/clustering/kmeans-init.rst
  • docs/source/api/algorithms/clustering/kmeans.rst
  • docs/source/api/algorithms/covariance/covariance.rst
  • docs/source/api/algorithms/covariance/index.rst
    ...

[napetrov]

can it also check that older Intel copyright owner that still exist?

[homksei]

removed this field so it won't be confusing, as it's not used for check.

[napetrov]

I would assume that overall check works and it would catch copyright that is not compliant

[napetrov]

We do have md files with copyrights - should we keep them for check? How many failures?

Might be as a next pr discussion on exclusion - fine to merge this one as is

[homksei]

/azp run

[homksei]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[icfaust]

This review mirrors this one: uxlfoundation/scikit-learn-intelex#2215 (review)

[icfaust]

Suggested change

	permissions:
	contents: read
	permissions: read-all

[icfaust]

Same question as in uxlfoundation/scikit-learn-intelex#2215

[homksei]

The check can leave comments on the pull request if it finds issues. For this, write permissions need to be granted for these scopes.