Add vpc and architectures option to the creation of lambda from source

[nnnkkk7]

What this PR does / why we need it:
I added vpc and architectures optional configuration to creation of lambda from source code as they did not exist.
Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

• How are users affected by this change:
• Is this breaking change:
• How to migrate (if breaking change):

[khanhtc1202]

/review

[github-actions]

## PR Analysis
  ### Main theme
    Enhancement
  ### PR summary
    The PR adds support for function architectures and VPC configuration when creating AWS Lambda functions through a custom client wrapper.
  ### Type of PR
    Enhancement

## PR Feedback:
  ### General suggestions
    The changes introduced in the PR are logical enhancements to the AWS Lambda client functionality. It adds the ability to specify function architectures and VPC configurations when creating a new lambda function, which are both important features for lambdas that need to operate within a VPC or require specific architectures. Ensuring the provided values match AWS expected formats should be accounted for to prevent runtime issues.
    
  ### Code feedback
    - relevant file: "pkg/app/piped/platformprovider/lambda/client.go"
      suggestion: "Consider validating the supported architectures before appending them to the 'architectures' slice to ensure the supplied architecture names are valid AWS Lambda architecture types. This can prevent the creation of a Lambda function with an invalid architecture and result in a better user experience by providing immediate feedback to the caller if an unsupported architecture is specified. Use 'types.Architecture' enumeration to check validity. [important]"
      relevant line: "+			architectures = append(architectures, types.Architecture(arch.Name))"
    - relevant file: "pkg/app/piped/platformprovider/lambda/client.go"
      suggestion: "For better performance, preallocate the 'architectures' slice with the exact required capacity since the size is known from 'fm.Spec.Architectures'. This can be achieved by using 'make([]types.Architecture, 0, len(fm.Spec.Architectures))'. [medium]"
      relevant line: "+		var architectures []types.Architecture"
    - relevant file: "pkg/app/piped/platformprovider/lambda/client.go"
      suggestion: "Ensure 'SecurityGroupIds' and 'SubnetIds' slices in 'types.VpcConfig' are properly validated for empty values or malformed inputs before attempting to create the Lambda function. This can prevent runtime API errors and improve overall robustness. [important]"
      relevant line: "+			SecurityGroupIds: fm.Spec.VPCConfig.SecurityGroupIDs,"
      
  ### Security concerns:
    no

[codecov]

Codecov Report

Attention: 12 lines in your changes are missing coverage. Please review.

Comparison is base (847b578) 30.84% compared to head (4e1785c) 30.79%.

Files	Patch %	Lines
pkg/app/piped/platformprovider/lambda/client.go	0.00%	12 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4723      +/-   ##
==========================================
- Coverage   30.84%   30.79%   -0.06%     
==========================================
  Files         221      221              
  Lines       25993    26005      +12     
==========================================
- Hits         8018     8008      -10     
- Misses      17325    17347      +22     
  Partials      650      650              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[khanhtc1202]

Thanks 🙌

[khanhtc1202]

@nnnkkk7 the DCO check is failed, please resign to the commit 🙏

[khanhtc1202]

@ffjlabo could you check this?

[ffjlabo]

Thank you for fixing 🚀