python_lambda: re-enable appsec tests

[florentinl]

Motivation

The problem is now fixed with: DataDog/datadog-lambda-python#681

Changes

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

tests/appsec/api_security/test_schemas.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/rasp/test_api10.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/rasp/test_cmdi.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/rasp/test_lfi.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/rasp/test_shi.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/rasp/test_sqli.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/rasp/test_ssrf.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/test_blocking_addresses.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/test_conf.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/test_fingerprinting.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/test_only_python.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/test_trace_tagging.py @DataDog/asm-libraries @DataDog/system-tests-core
tests/appsec/waf/test_blocking.py @DataDog/asm-libraries @DataDog/system-tests-core