fix: splitup the policy creation if too many parameters are created …

[lenderom]

When creating a large set of parameters the maxium policy size of is exceeded:

This PR improves the parameter policy creation by splitting up the policy, if it would exceed the maximum policy size.

Additionally the property keySeperator was renamed to keySeparator to match flattenSeparator.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.70%. Comparing base (8caaadb) to head (082e6d7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1050   +/-   ##
=======================================
  Coverage   75.70%   75.70%           
=======================================
  Files           3        3           
  Lines         354      354           
=======================================
  Hits          268      268           
  Misses         49       49           
  Partials       37       37           

Flag	Coverage Δ
go-lambda	75.70% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[lenderom]

I would like to test a prebuild version now, to check if it work's like expected.

[lenderom]

I tested it, resulting in a different error. The policy split up worked, but now the respone object of the custom resource is too large:

[lenderom]

I sucessfully deploy this fixed version with 120 parameters. The policy was split up in 2,5 managed policys.