🐛 Add CAPI metadata.yaml to the e2e

[namnx228]

This PR adds CAPI metadata.yaml to the e2e folder, so the problem with clusterctl init can be solved. This metadata.yaml differs from the one in the root directory. It documents the release series of cluster-api provider, so it is the file located in the root directory of cluster-api repo.

failed to run clusterctl init
    Unexpected error:
        <*errors.withStack | 0xc001656870>: {
            error: <*errors.withMessage | 0xc0008fb2e0>{
                cause: <*errors.withStack | 0xc001656840>{
                    error: <*errors.withMessage | 0xc0008fb2c0>{
                        cause: <*fs.PathError | 0xc000b8a000>{
                            Op: "stat",
                            Path: "/home/****/tested_repo/_artifacts/repository/cluster-api/v0.4.0/metadata.yaml",
                            Err: <syscall.Errno>0x2,
                        },
                        msg: "failed to read file \"/home/****/tested_repo/_artifacts/repository/cluster-api/v0.4.0/metadata.yaml\" from local release v0.4.0",
                    },
                    stack: [0x193fcc5, 0x193c7d6, 0x194d904, 0x194d1be, 0x1976742, 0x197df55, 0x1a00bfc, 0x1a05aa8, 0x78b123, 0x78ad3c, 0x78a307, 0x790e2f, 0x7904d2, 0x7b90b1, 0x7b8bc7, 0x7b83b7, 0x7baac6, 0x7c8178, 0x7c7e27, 0x19ff3b8, 0x527c2f, 0x4744e1],
                },
                msg: "failed to read \"metadata.yaml\" from the repository for provider \"cluster-api\"",
            },
            stack: [0x193c91d, 0x194d904, 0x194d1be, 0x1976742, 0x197df55, 0x1a00bfc, 0x1a05aa8, 0x78b123, 0x78ad3c, 0x78a307, 0x790e2f, 0x7904d2, 0x7b90b1, 0x7b8bc7, 0x7b83b7, 0x7baac6, 0x7c8178, 0x7c7e27, 0x19ff3b8, 0x527c2f, 0x4744e1],
        }
        failed to read "metadata.yaml" from the repository for provider "cluster-api": failed to read file "/home/****/tested_repo/_artifacts/repository/cluster-api/v0.4.0/metadata.yaml" from local release v0.4.0: stat /home/****/tested_repo/_artifacts/repository/cluster-api/v0.4.0/metadata.yaml: no such file or directory
    occurred

[namnx228]

/test-integration
/test-v1a5-e2e

[namnx228]

/assign @furkatgofurov7
/cc @wgslr
/cc @fmuyassarov

[namnx228]

/test-integration
/test-v1a5-e2e

[namnx228]

/hold

[namnx228]

/test-v1a5-e2e

[wgslr]

/approve

[namnx228]

/hold cancel

[namnx228]

/test-integration
/test-v1a5-e2e

[furkatgofurov7]

/approve

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: furkatgofurov7, wgslr

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 [furkatgofurov7]

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

[Rozzii]

/lgtm

[metal3-io-bot]

@Rozzii: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fmuyassarov]

/lgtm