Standardize ACK controller logs - `FieldExport` format cleanup

[a-hilaly]

While reviewing log formats in kro#462, we noticed that ACK logs are already quite close to being standardized — using structured JSON logs with useful fields like controller, controllerGroup, and controllerKind.

However, there are some minor inconsistencies, particularly with FieldExport log entries, where values like the controller name may include embedded version/kind info (e.g "controller": "field-export.ec2.services.k8s.aws/v1alpha1, Kind=Subnet"). These could be cleaned up for better parsing and consistency across controllers

AI: we should normalize FieldExport logs to use the same structure as other controllers and avoid embedding version/kind info in the controller field.

I had a quick chat with Matthew from Azure ASO team, and we agreed that all of our controllers (ACK and ASO) should follow the same recommended format - like we're doing in KRO 🚀

[github-actions]

Hello @a-hilaly 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.

[ack-bot]

Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale

[ack-bot]

Stale issues rot after 60d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 60d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle rotten