refactor: Move Go code to dedicated backend/ directory

[machadovilaca]

No description provided.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[machadovilaca]

/cc @DavidRajnoha @jgbernalp

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: machadovilaca
Once this PR has been reviewed and has the lgtm label, please assign kyoto for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[DavidRajnoha]

/test all

[DavidRajnoha]

The proposed structure is aligned with what I described on the call.

There seems to be some issue with the PR tests now, I will retrigger them later if needed, their pass is neccessary to ensure that the change is reflected in our automation.

[machadovilaca]

/test all

[jgbernalp]

Not sure if we need this. Even if the backed is on the root, it has its own folders which will include testing and e2e. e2e test for the frontend are already contained inside the web folder. If possible I'd like to keep this structure as it aligns with all the other observability plugins and makes it consistent for productization. I thought the suggestion was to include the specific e2e tests for the backend into its own folder.

[openshift-ci]

@machadovilaca: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[machadovilaca]

Not sure if we need this. Even if the backed is on the root, it has its own folders which will include testing and e2e. e2e test for the frontend are already contained inside the web folder. If possible I'd like to keep this structure as it aligns with all the other observability plugins and makes it consistent for productization. I thought the suggestion was to include the specific e2e tests for the backend into its own folder.

@DavidRajnoha Given Gabriel comment, should we keep the current structure, in the alertmanagement work we are planning to add internal/ and test/e2e/ packages, would you be okay with that?