fix lambda ASF API updates

[alexrashed]

Since lambda is a keyword, it cannot easily be used in imports. This is why the lambda service module is called awslambda instead of lambda (as the real service name is).
But the scaffold's upgrade function only detects services which are named the same way as the service (with some escaping logic). This is why the generated services cannot just be renamed.

This PR fixes the scaffold to fix the automatic ASF API updates for lambda by:

• Adding a keyword escaping logic for service names in the scaffold.
• Renaming the ASF API package from awslambda to lambda_ (which is the escaped service name).
• Re-generating the API with the latest version of botocore.

I have verified that there are no other generated APIs which have a different name than the service.
Here's the bash snippet I created to verify that:

 find . -type d | grep -v __pycache__"" | grep -v -e "\.\$" | cut -c 3- | tr _ - | sed 's/-$//' \
   | xargs -I '{}' \
   bash -c 'SERVICE={} && cd ~/Repos/localstack-ext/.venv/lib/python3.10/site-packages/botocore/data && test -d $SERVICE || (echo $SERVICE not found; exit 1)'

[coveralls]

Coverage decreased (-0.003%) to 91.509% when pulling 25666e1 on fix-lambda-asf-api-updates into 0da0472 on master.

[github-actions]

LocalStack integration with Pro

       3 files  ±0         3 suites  ±0   59m 15s ⏱️ - 3m 40s
1 119 tests ±0  1 079 ✔️  - 1  40 💤 +1  0 ❌ ±0 
1 434 runs  ±0  1 365 ✔️  - 1  69 💤 +1  0 ❌ ±0 

Results for commit 25666e1. ± Comparison against base commit 0da0472.

♻️ This comment has been updated with latest results.

[thrau]

sorry @alexrashed ! i think #6409 created the conflict

[dominikschubert]

LGTM, thanks for fixing this 👍

[dfangl]

🎉