Fix AccessKey.iam reconciliation

[ulucinar]

Description of your changes

Related issue: https://github.com/crossplane/upjet/issues/416 Depends on: https://github.com/crossplane/upjet/pull/417

If the MR API has a spec.forProvider.status field and there are sensitive attributes, then fieldpath.Paved.ExpandWildcards complains instead of expanding as an empty slice, which breaks the reconciliation. Please refer to https://github.com/crossplane/upjet/pull/417 for more context on the issue.

This PR bumps upjet to v1.4.1.

I have:

• [x] Read and followed Crossplane's contribution process.
• [x] Run make reviewable to ensure this PR is ready for review.
• [ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

• Manually verified AccessKey.iam now successfully reconciles and its connection details secret contains all the keys from the v1.4.0 version of the provider: attribute.secret, attribute.ses_smtp_password_v4, password, username
• Via uptest run here: https://github.com/crossplane-contrib/provider-upjet-aws/actions/runs/9399021904
• Also validated that the current spec.initProvider behavior is not broken with the uptest run of User.mq resource here: https://github.com/crossplane-contrib/provider-upjet-aws/actions/runs/9399082530

[ulucinar]

/test-examples="examples/iam/v1beta1/accesskey.yaml"

[ulucinar]

/test-examples="examples/mq/v1alpha1/user.yaml"

[ulucinar]

/test-examples="examples/iam/v1beta1/accesskey.yaml"