Add Support for Scraper resource in amp provider

[nujragan93]

Description of your changes

Add support for AMP Prometheus Scraper resource

Fixes #

I have:

• Read and followed Crossplane's contribution process.
• Run make generate and committed the results (ideally in a separate commit).
• Not made any manual changes to generated files, and verified this with make check-diff.

How has this code been tested

• Manual Testing Running AMP Provider with crossplane

• Tested creating, observing and deletion of the resource

• Tested referencing workspace object from scraper resource

[jeanduplessis]

/test-examples="examples/amp/cluster/v1beta1/scraper.yaml"

[nujragan93]

@jeanduplessis looks like the e2e failed because the scraper was in a Creating state, I see that the external name of the scraper id was flipping between two IDs, I cant seem to understand the issue causing this, any help is appreciated

[erhancagirici]

@nujragan93 thanks for the PR! Looks good overall, left some minor change requests.

I checked this and was able to reproduce the issue. This looks like to be an issue at upjet causing an superfluous diff, which I am investigating with a potential fix. I'll further update here. For that no action is needed from your side.

[nujragan93]

@erhancagirici Thanks for your review, Added amp config to namespaced type.

[erhancagirici]

/test-examples="examples/amp/cluster/v1beta1/scraper.yaml"

[erhancagirici]

After consuming the fix at Upjet, the Uptest run passed. Linter is complaining about some deprecated field usage (unrelated to this PR) after upjet bump, so opened a dedicated PR #1931 to handle the upjet bump. Will rebase this PR after that one is merged.

[erhancagirici]

/test-examples="examples/amp/cluster/v1beta1/scraper.yaml"

[erhancagirici]

Thanks @nujragan93 for the contribution 🙌 ! I've rebased the PR to latest main with the fix included, and now it passes the tests. LGTM!