fix: resolve false-positive configuration changes for Layers and Logg…

[jfeddern]

…ingConfig

Issue #, if available:
#50

Description of changes:

Problem

The action incorrectly reported configuration changes when comparing Lambda function configurations, specifically for Layers and LoggingConfig.
This occurred because GetFunctionConfiguration returns different data structures than what UpdateFunctionConfiguration accepts:

• Layers: AWS returns array of Layer objects (with Arn, CodeSize, SigningProfileVersionArn, SigningJobArn) but UpdateFunctionConfiguration accepts array of ARN strings
• LoggingConfig: AWS adds read-only LogGroup field that users cannot set via UpdateFunctionConfiguration

This caused the deepEqual comparison to always fail, triggering unnecessary configuration updates and misleading users.

Solution

Added normalizeConfigValue() function to normalize configuration values before comparison:

• For Layers: Extract ARN strings from Layer objects
• For LoggingConfig: Remove read-only LogGroup field

Modified hasConfigurationChanged() to use normalization, ensuring accurate comparison between current AWS state and user-provided config.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.