[Bug]: Lambda loggingConfiguration doesn't work

[HeinanCA]

Is there an existing issue for this?

• I have searched the existing issues

Affected Resource(s)

lambda.aws.upbound.io/v1beta1 - Function

Resource MRs required to reproduce the bug

apiVersion: lambda.aws.upbound.io/v1beta1
kind: Function
metadata:
name: blue-team-lambda
spec:
forProvider:
architectures:
- x86_64
handler: blue_team.lambda_handler
packageType: Zip
roleRef:
name: blue-team-role
region: us-east-1
runtime: python3.12
logFormat: "JSON"
loggingConfig: # TODO This needs some proper investigation
- logGroup: /aws/lambda/ommitted
- logFormat: "JSON"
- applicationLogLevel: "INFO"
- systemLogLevel: "INFO"
environment:
- variables:
DUMMY_DAYS: "90"
s3Bucket: dev-lambdas
s3Key: ommitted
timeout: 30
memorySize: 128
tags:
"Team": "TeamBlue"
"Environment": "Develop"

providerConfigRef:
name: default

Steps to Reproduce

Apply the following YAML to deploy a lambda. Nothing happens on the cluster (lambda is deployd with no logging configuration). After ~6 hours --> cluster shows an error message "failed to sync cluster https://172.20.0.1:443: failed to load initial state of resource Function.lambda.aws.upbound.io: conversion webhook for lambda.aws.upbound.io/v1beta1, Kind=Function failed: cannot convert from the spoke version "v1beta1" to the hub version "v1beta2": cannot apply the PavedConversion for the "aws_lambda_function" object: failed to convert the source map in mode "toEmbeddedObject" with source API version "*", target API version "v1beta2": singleton list, at the field path loggingConfig, must have a length of at most 1 but it has a length of 4"

What happened?

Got an error message:
failed to sync cluster https://172.20.0.1:443: failed to load initial state of resource Function.lambda.aws.upbound.io: conversion webhook for lambda.aws.upbound.io/v1beta1, Kind=Function failed: cannot convert from the spoke version "v1beta1" to the hub version "v1beta2": cannot apply the PavedConversion for the "aws_lambda_function" object: failed to convert the source map in mode "toEmbeddedObject" with source API version "*", target API version "v1beta2": singleton list, at the field path loggingConfig, must have a length of at most 1 but it has a length of 4

This led to us having to clear up the crossplane deployment

Relevant Error Output Snippet

Crossplane Version

1.18

Provider Version

1.19.0

Kubernetes Version

1.30.6

Kubernetes Distribution

EKS

Additional Info

No response