feat: add datasource for AWS Lambda Layers

[kayman-mk]

Changes

This PR adds a new datasource to update the versioned layer arns for AWS Lambda Layers.

Context

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[kayman-mk]

Reopens #19081

I stopped working on that PR because I found out that you usually do not have the lambda:listLayerVersion policy for layers you do not own. So I thought this whole datasource didn't make any sense. But in fact it is useful as we found out in a team internal discussion today:

• you can use it to update lambda layers you own
• you can ask the maintainer of the layer you do not own to add the respective permission so Renovate can list the version numbers as well

aws lambda add-layer-version-permission \
    --layer-name my-layer \
    --statement-id xaccount \
    --action lambda:ListLayerVersions  \
    --principal 123456789012 \
    --version-number 1

[kayman-mk]

Still have to work on the documentation

[rarkins]

@kayman-mk Every time you update the branch it resets (disables) the CI approvals. It's best you don't commit to this branch unless you have changes or need to resolve a conflict

[kayman-mk]

Ah, ok. Thought it needs to be on the HEAD to be merged. Sorry.

[rarkins]

GitHub's merge queue ensures that it's tested against the latest main commit before merging so we don't need to update PRs individually unless there's a conflict or a high chance that another PR broke the open one

[kayman-mk]

Still struggeling with the pnpm-lock.yaml. How can I regenerate the file so it includes my changes?

[kayman-mk]

@viceice Is this assumption correct? If not: how to catch this error?

try {
  FilterParser.parse(xxxx);
} catch (e) {
  // log error and return null
}

Looks ugly and I guess there is a better option. Checking the existing source, I didn't find any.