feat: Do not set Status.AtProvider.LastUsedAt for IAM roles by default

[max-melentyev]

Because it can call frequent unnecessary reconciliations of dependent resources.

Description of your changes

LastUsedAt is updated frequently and triggers unnecessary reconciliations of dependent resources.

I presumed that this field is used rarely and reasonable default would be not to update it on every reconciliation, even though this will be a breaking change.

Please let me know if you think it's better to use IGNORE_LAST_USED_AT annotation instead.

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

new test case

[MisterMX]

Can you give more information about the issue you are experiencing? Which reconcilations are triggered by an update of the roles status information?

[max-melentyev]

We have a CRD and its controller manages roles used by the CRD. This controller watches all its managed resources including roles to make sure these resources exist and have required specs. This makes controller-runtime to run controller every time watched resource changes. Roles are used often and this makes CRD controller run constantly even if nothing else happens.

[MisterMX]

I'm not very confident with adding this exception for a very special use case. As long as there no other users having the same issue in their environment I would suggest to not merge this and propose to use a custom fork instead.

[max-melentyev]

@MisterMX What if I change it to the "default to the current behaviour" and make new behaviour optional?