chore(deps): Bump fast-xml-parser and @aws-sdk/client-ssm

[dependabot]

Bumps fast-xml-parser to 4.2.4 and updates ancestor dependency @aws-sdk/client-ssm. These dependencies need to be updated together.

Updates fast-xml-parser from 3.19.0 to 4.2.4

Release notes

Sourced from fast-xml-parser's releases.

Security Fix

Update to this release if you use entity parsing in Fast XML Parser.

v4

• Generating different combined, parser only, builder only, validator only browser bundles
• Keeping cjs modules as they can be imported in cjs and esm modules both. Otherwise refer esm branch.

4.0.0-beta.8 / 2021-12-13

• call tagValueProcessor for stop nodes

4.0.0-beta.7 / 2021-12-09

• fix Validator bug when an attribute has no value but '=' only
• XML Builder should suppress unpaired tags by default.
• documents update for missing features
• refactoring to use Object.assign
• refactoring to remove repeated code

4.0.0-beta.6 / 2021-12-05

• Support PI Tags processing
• Support suppressBooleanAttributes by XML Builder for attributes with value true.

4.0.0-beta.5 / 2021-12-04

• fix: when a tag with name "attributes"

4.0.0-beta.4 / 2021-12-02

• Support HTML document parsing
• skip stop nodes parsing when building the XML from JS object
• Support external entites without DOCTYPE
• update dev dependency: strnum v1.0.5 to fix long number issue

4.0.0-beta.3 / 2021-11-30

• support global stopNodes expression like "*.stop"
• support self-closing and paired unpaired tags
• fix: CDATA should not be parsed.
• Fix typings for XMLBuilder (#396)(By Anders Emil Salvesen)
• supports XML entities, HTML entities, DOCTYPE entities

⚠️ 4.0.0-beta.2 / 2021-11-19

• rename attrMap to attibutes in parser output when preserveOrder:true
• supports unpairedTags

⚠️ 4.0.0-beta.1 / 2021-11-18

• Parser returns an array now
  • to make the structure common
  • and to return root level detail
• renamed cdataTagName to cdataPropName
• Added commentPropName
• fix typings

⚠️ 4.0.0-beta.0 / 2021-11-16

... (truncated)

Changelog

Sourced from fast-xml-parser's changelog.

Note: If you find missing information about particular minor version, that version must have been changed without any functional change in this library.

4.2.4 / 2023-06-06

• fix security bug

4.2.3 / 2023-06-05

• fix security bug

4.2.2 / 2023-04-18

• fix #562: fix unpaired tag when it comes in last of a nested tag. Also throw error when unpaired tag is used as closing tag

4.2.1 / 2023-04-18

• fix: jpath after unpaired tags

4.2.0 / 2023-04-09

• support updateTag parser property

4.1.4 / 2023-04-08

• update typings to let user create XMLBuilder instance without options (#556) (By Patrick)
• fix: IsArray option isn't parsing tags with 0 as value correctly #490 (#557) (By Aleksandr Murashkin)
• feature: support oneListGroup to group repeated children tags udder single group

4.1.3 / 2023-02-26

• fix #546: Support complex entity value

4.1.2 / 2023-02-12

• Security Fix

4.1.1 / 2023-02-03

• Fix #540: ignoreAttributes breaks unpairedTags
• Refactor XML builder code

4.1.0 / 2023-02-02

• Fix '' in DTD comment throwing an error. (#533) (By Adam Baker)
• Set "eNotation" to 'true' as default

4.0.15 / 2023-01-25

• make "eNotation" optional

4.0.14 / 2023-01-22

• fixed: add missed typing "eNotation" to parse values

4.0.13 / 2023-01-07

• preserveorder formatting (By mdeknowis)
• support transformAttributeName (By Erik Rothoff Andersson)

4.0.12 / 2022-11-19

• fix typescript

4.0.11 / 2022-10-05

... (truncated)

Commits

• ecf6016 update package
• 0955739 fix: security bug
• abfee16 update package detail
• 39b0e05 fix security bug
• e7728af update funding detail
• c7b3cea update package detail
• 6511e07 fix unpaired tag
• b6cad83 Update bug-report-or-unexpected-output.md
• dfd25bf Update greetings.yml
• b4d3011 update funding detail
• Additional commits viewable in compare view

Updates @aws-sdk/client-ssm from 3.131.0 to 3.350.0

Release notes

Sourced from @​aws-sdk/client-ssm's releases.

v3.350.0

3.350.0(2023-06-09)

Documentation Changes

• client-acm-pca: Document-only update to refresh CLI documentation for AWS Private CA. No change to the service. (72364d27)

New Features

• client-connect: This release adds search APIs for Prompts, Quick Connects and Hours of Operations, which can be used to search for those resources within a Connect Instance. (37fc985c)

Bug Fixes

• node-http-handler: stop waiting for continue event on error (#4805) (20a210e1)

---

For list of updated packages, view updated-packages.md in assets-3.350.0.zip

v3.349.0

3.349.0(2023-06-08)

New Features

• clients: update client endpoints as of 2023-06-08 (0c458b2b)
• client-payment-cryptography: Initial release of AWS Payment Cryptography Control Plane service for creating and managing cryptographic keys used during card payment processing. (6658867b)
• client-timestream-write: This release adds the capability for customers to define how their data should be partitioned, optimizing for certain access patterns. This definition will take place as a part of the table creation. (bba2033a)
• client-athena: You can now define custom spark properties at start of the session for use cases like cluster encryption, table formats, and general Spark tuning. (655c2dd0)
• client-payment-cryptography-data: Initial release of AWS Payment Cryptography DataPlane Plane service for performing cryptographic operations typically used during card payment processing. (f9309133)
• client-comprehendmedical: This release supports a new set of entities and traits. (83e84301)
• client-service-catalog: New parameter added in ServiceCatalog DescribeProvisioningArtifact api - IncludeProvisioningArtifactParameters. This parameter can be used to return information about the parameters used to provision the product (ea91820f)

---

For list of updated packages, view updated-packages.md in assets-3.349.0.zip

v3.348.0

3.348.0(2023-06-07)

Documentation Changes

• client-direct-connect: This update corrects the jumbo frames mtu values from 9100 to 8500 for transit virtual interfaces. (f96195ba)

New Features

• client-customer-profiles: This release introduces event stream related APIs. (52630226)
• client-cloudformation: AWS CloudFormation StackSets is updating the deployment experience for all stackset operations to skip suspended AWS accounts during deployments. StackSets will skip target AWS accounts that are suspended and set the Detailed Status of the corresponding stack instances as SKIPPED_SUSPENDED_ACCOUNT (83514dbf)
• client-emr-containers: EMR on EKS adds support for log rotation of Spark container logs with EMR-6.11.0 onwards, to the StartJobRun API. (9a4e1431)

... (truncated)

Changelog

Sourced from @​aws-sdk/client-ssm's changelog.

3.350.0 (2023-06-09)

Note: Version bump only for package @​aws-sdk/client-ssm

3.348.0 (2023-06-07)

Note: Version bump only for package @​aws-sdk/client-ssm

3.347.1 (2023-06-07)

Note: Version bump only for package @​aws-sdk/client-ssm

3.347.0 (2023-06-06)

Note: Version bump only for package @​aws-sdk/client-ssm

3.345.0 (2023-06-02)

Note: Version bump only for package @​aws-sdk/client-ssm

3.344.0 (2023-06-01)

Note: Version bump only for package @​aws-sdk/client-ssm

3.342.0 (2023-05-30)

... (truncated)

Commits

• 28aae5c Publish v3.350.0
• 4164757 Publish v3.348.0
• 7529755 Publish v3.347.1
• db169f4 Publish v3.347.0
• 5da2084 Publish v3.345.0
• 4c2fd64 Publish v3.344.0
• d78d640 Publish v3.342.0
• 44a18a3 Publish v3.341.0
• f4531fe Publish v3.338.0
• 1982984 docs(codegen): run codegen for awslabs/smithy-typescript#770 (#4746)
• 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.