Install Manifest in Upbound Marketplace uses deprecated `apiVersion` (`v1alpha1` instead of `v1`)

### Description

I noticed an inconsistency between the Install Manifest shown in the Upbound Marketplace for `provider-http` and the manifests in this GitHub repository.

In the Upbound Marketplace, clicking the **Install Manifest** button provides a manifest that uses:

```yaml
apiVersion: pkg.crossplane.io/v1alpha1
```

However, this `apiVersion` is deprecated and should be updated to:

```yaml
apiVersion: pkg.crossplane.io/v1
```

The GitHub repository already reflects the correct `pkg.crossplane.io/v1` `apiVersion`, so this appears to be a sync issue between the repository and the Upbound Marketplace.

### Expected Behavior

The Install Manifest shown in the Upbound Marketplace should use:

```yaml
apiVersion: pkg.crossplane.io/v1
```

so that it matches the current Crossplane API version and the manifests in this repository.

### Actual Behavior

The Install Manifest in the Upbound Marketplace still uses:

```yaml
apiVersion: pkg.crossplane.io/v1alpha1
```

### Additional Context

I contacted Upbound support about this, and they suggested opening an issue in this repository so it can be tracked and resolved.

### References

- Upbound Marketplace | [provider-http overview](https://marketplace.upbound.io/providers/crossplane-contrib/provider-http/v1.0.13)
- GitHub | [provider http YAML installation](https://github.com/crossplane-contrib/provider-http?tab=readme-ov-file#installation)

Start by reviewing the repository's installation manifest and README installation section, then compare them with the Install Manifest at the linked Upbound Marketplace provider page. The work is done when the Marketplace manifest uses pkg.crossplane.io/v1 and matches the repository's current manifest.

Written by the indexing model from the issue text.