Add generated files by the OSPO team

[antgamdia]

Description of the change

As per #4757, we are required to update the "legal" files to comply with our Open Source compliance team's guidelines. This PR is to add the generated files for our v2.4.6 release.

Benefits

OSPO-compliant legal files, finally!

Possible drawbacks

N/A

Applicable issues

• fixes OSM onboarding for Kubeapps #4757

Additional information

Marking as a draft since the actual files are still under review. Also, there are some ongoing questions I want to clarify before merging; but I wanted to send the PR asap so that others can make some comments and we have time to address them.

[netlify]

✅ Deploy Preview for kubeapps-dev canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	4dfc63e
🔍 Latest deploy log	https://app.netlify.com/sites/kubeapps-dev/deploys/62b41bd16d082c00083f36b5

[antgamdia]

For the record - and to be the best of my knowledge -the copyright information in the license text must represent the current copyright holder (under the terms described in the license, which is (and always have been) Apache2.0). This means:

Copyright (c) 2017-2022 VMware, Inc. All rights reserved.

On the other hand, the copyright headers in the source file are just recommended. In this case, for open-source projects where we may not know whether all of the original authors were employees of the same company, using something generic like "the Kubeapps contributors" might be ok.
The formula for this text is: 1) the copyright symbol ©, the word "Copyright", or the abbreviation "Copr.", 2) the year of publication, 3) the name of the copyright owner.

For instance:

// Copyright 2021-2022 the Kubeapps contributors.
// SPDX-License-Identifier: Apache-2.0

Therefore, no extra changes are required in the copyright headers of our source files.

[antgamdia]

I've added the approved open_source_licenses.txt file. Marking as ready and merging.