Allow contributor copyright notices in RuboCop

[AkashKumar7902]

What does this PR change?

Broadens the testsuite RuboCop copyright rule to accept notices from any copyright holder instead of requiring SUSE LLC.

The copyright cop remains enabled and the existing SUSE autocorrect template is unchanged. This allows contributor-owned files to keep accurate attribution and unblocks the RuboCop checks on #12077 and #12341.

End-User Impact & Release Notes

No end-user impact. This only changes testsuite lint configuration.

• DONE

Codespace

GUI diff

No difference.

• DONE

Documentation

• No documentation needed: only internal and user-invisible lint configuration changes.

• DONE

Test coverage

• RuboCop 1.82.1 passes on all testsuite Ruby files scanned by the workflow.

• A contributor-owned copyright notice passes.

• A Ruby file without a copyright notice is still rejected by Style/Copyright.

• DONE

Links

Issue(s): none
Related PRs: #12077, #12341
Port(s): none

• DONE

Changelogs

• No changelog needed

Re-run a test

• Re-run test "changelog_test"
• Re-run test "backend_unittests_pgsql"
• Re-run test "java_pgsql_tests"
• Re-run test "schema_migration_test_pgsql"
• Re-run test "susemanager_unittests"
• Re-run test "frontend_checks"
• Re-run test "spacecmd_unittests"

Before you merge

Check How to branch and merge properly!

[github-actions]

👋 Hello! Thanks for contributing to our project.
Acceptance tests will take some time (approx. 1h), please be patient ☕

You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/12504/checks
Once tests finish, if they fail, you can check 👀 the cucumber report. See the link at the output of the action.
You can also check the artifacts section, which contains the logs at https://github.com/uyuni-project/uyuni/pull/12504/checks.

If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code.

Reference tests:

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary_parallel.yml?query=event%3Aschedule

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary.yml?query=event%3Aschedule

KNOWN ISSUES

Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience.

For more tips on troubleshooting, see the troubleshooting guide.

Happy hacking!

[cbosdo]

LGTM