build(deps-dev): bump moto from 5.1.11 to 5.1.19

[dependabot]

Bumps moto from 5.1.11 to 5.1.19.

Changelog

Sourced from moto's changelog.

5.1.19

Docker Digest for 5.1.19: sha256:1bba01d147a15d14a5816b69ee6d346ba04bd43baab4a3a27a55c368ecc2bb90

General:
    * Removed support for ElasticTranscoder, now that AWS has also deprecated this service
New Methods:

* ACM-PCA:

* revoke_certificate()
* DSQL:
    * delete_cluster()
    * get_vpc_endpoint_service_name()
    * list_tags_for_resource()


FSX:

describe_backups()



SESv2:

list_tags_for_resource()
tag_resource()
untag_resource()



VPC Lattice:

delete_auth_policy()
delete_resource_policy()
get_auth_policy()
get_resource_policy()
put_auth_policy()
put_resource_policy()





Miscellaneous:

* DynamoDB: put_item() now correctly validates numeric and boolean values

* EC2: describe_instances() now returns the correct status for BlockDeviceMappings.Ebs.Status (attached, instead of in-use)

* EC2: describe_network_acls() now supports the 'association.association-id' Filter

* ELBv2: modify_load_balancer_attributes() no longer fails when modifying the 'health_check_logs.s3.enabled' attribute

* ResourceGroupsTaggingAPI: get_resources() now supports the SESv2 resources: ConfigurationSets, ContactLists, DedicatedIpPool, EmailIdentity

* Route53: change_tags_for_resource() no longer throws an error for removing a non-existing tag

* S3: list_object_versions() now correctly calculates the IsLatest-attribute

* Scheduler: list_schedules() and list_schedule_groups() now support pagination

* SecretsManager: batch_get_secret_value() now returns error handling for unknown secrets

* SSM: put_parameter() now returns the Tier-attribute

5.1.18

Docker Digest for 5.1.18: sha256:c99ea4ab0881e1d95af5601c2cd42ef4dac15eefdf6597532c59d9631068818a

General:

... (truncated)

Commits

• 714c6d8 Pre-Release: Up Version Number
• dadd622 Prep release 5.1.19 (#9597)
• 09ce366 chore: update SSM default parameters (#9595)
• b543be0 Autoscaling: Improve parity around LaunchTemplates (#9596)
• dae4435 chore: update EC2 Instance Offerings (#9592)
• d15adc0 chore: update EMR Instance Types (#9591)
• 409f728 Upgrade ruff to 0.14.10 (current latest). (#9588)
• b1055ca EC2: describe_network_acls() now supports the 'association.association-id' Fi...
• 393e41e SSM: add Tier to PutParameter response (#9590)
• 8d4f40c remove pylint mention from docs, remove pylint comments (#9587)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[github-actions]

🔒 Container Security Scan

Image: prowler:796067b
Last scan: 2026-01-15 13:42:43 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	3
Total	3

3 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy