fix(lambda): bump @aws-lambda-powertools/tracer from 1.14.2 to 1.16.0 in /lambdas (#3622)

Bumps
[@aws-lambda-powertools/tracer](https://github.com/aws-powertools/powertools-lambda-typescript)
from 1.14.2 to 1.16.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/aws-powertools/powertools-lambda-typescript/releases"><code>@​aws-lambda-powertools/tracer</code>'s
releases</a>.</em></p>
<blockquote>
<h2>v1.16.0</h2>
<h2>Summary</h2>
<p>In this minor release we are adding support for two new environments
variables to configure the log level in Logger.</p>
<p>You can now configure the log level of for Logger using two new
environment variables: <code>AWS_LAMBDA_LOG_LEVEL</code> and
<code>POWERTOOLS_LOG_LEVEL</code>. The new environment variables will
work along the existing <code>LOG_LEVEL</code> variable that is now
considered legacy and will be removed in the future.</p>
<p>Setting the log level now follows this order:</p>
<ol>
<li><code>AWS_LAMBDA_LOG_LEVEL</code> environment variable</li>
<li>Setting the log level in code using the <code>logLevel</code>
constructor option, or by calling the <code>logger.setLogLevel()</code>
method</li>
<li><code>POWERTOOLS_LOG_LEVEL</code> environment variable</li>
</ol>
<p>We have also added a <a
href="https://docs.powertools.aws.dev/lambda/typescript/1.16.0/core/logger/#log-levels">new
section to the docs</a> to highlight the new behavior.</p>
<h2>Changes</h2>
<h2>🌟New features and non-breaking changes</h2>
<ul>
<li>feat(logger): add support for <code>AWS_LAMBDA_LOG_LEVEL</code> and
<code>POWERTOOLS_LOG_LEVEL</code> (<a
href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1795">#1795</a>)
by <a
href="https://github.com/dreamorosi"><code>@​dreamorosi</code></a></li>
</ul>
<h2>📜 Documentation updates</h2>
<ul>
<li>feat(logger): add support for <code>AWS_LAMBDA_LOG_LEVEL</code> and
<code>POWERTOOLS_LOG_LEVEL</code> (<a
href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1795">#1795</a>)
by <a
href="https://github.com/dreamorosi"><code>@​dreamorosi</code></a></li>
</ul>
<h2>This release was made possible by the following contributors:</h2>
<p><a
href="https://github.com/dreamorosi"><code>@​dreamorosi</code></a></p>
<h2>v1.15.0</h2>
<h2>Summary</h2>
<p>This release brings support for the new Node.js 20 AWS Lambda managed
runtime as well as tweaking how the Metrics utility emits logs under the
hood.</p>
<h3>Node.js 20 support</h3>
<p>With this release we are excited to announce that Powertools for AWS
Lambda (TypeScript) is compatible with the <code>nodejs20.x</code> AWS
Lambda managed runtime 🎉.</p>
<p>The toolkit and our public <a
href="https://docs.powertools.aws.dev/lambda/typescript/latest/#lambda-layer">Lambda
Layers</a> are both compatible with the new runtime and no code change
should be required on your part.</p>
<h3>Metrics</h3>
<p>The Metrics utility emits logs using the Embedded Metric Format
(EMF). Prior to this release, the logs were emitted using the global
<code>console</code> object. This makes it so that in addition to the
payload of the log, AWS Lambda adds the request id and timestamp of the
log.</p>
<p>For most customers, and especially those who consume the metrics in
Amazon CloudWatch, this is fine as CloudWatch is able to parse the EMF
content and create custom metrics. For customers who instead want to
send the metrics to third party observability providers the presence of
these strings means having an extra parsing step.</p>
<p>To support these use cases, and to align with the behavior of the
Logger utility, the Metrics utility now uses a dedicated instance of the
<code>Console</code> object, which allows it to emit only the content of
EMF metric. Just like for the Logger, this behavior can be reverted for
development environments by setting the <code>POWERTOOLS_DEV</code>
environment variable to a truthy value (i.e. <code>true</code>,
<code>yes</code>, <code>1</code>, <code>on</code>, etc.).</p>
<p>When <code>POWERTOOLS_DEV</code> is enabled, the Metrics utility
reverts to using the global <code>console</code> object. This allows
customers to place mock and spies and optionally override the
implementation for testing purposes.</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md"><code>@​aws-lambda-powertools/tracer</code>'s
changelog</a>.</em></p>
<blockquote>
<h1><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v1.15.0...v1.16.0">1.16.0</a>
(2023-11-16)</h1>
<h3>Features</h3>
<ul>
<li><strong>logger:</strong> add support for
<code>AWS_LAMBDA_LOG_LEVEL</code> and <code>POWERTOOLS_LOG_LEVEL</code>
(<a
href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1795">#1795</a>)
(<a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/e69abfb5f1b5d3bf993ac2fe66fae85a85af9905">e69abfb</a>)</li>
</ul>
<h1><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v1.14.2...v1.15.0">1.15.0</a>
(2023-11-14)</h1>
<h3>Features</h3>
<ul>
<li><strong>maintenance:</strong> add support for nodejs20.x runtime (<a
href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1790">#1790</a>)
(<a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/6b9b1bcb9baf4b3d8e0e5ec6709594aca09bb033">6b9b1bc</a>)</li>
<li><strong>metrics:</strong> log directly to stdout (<a
href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1786">#1786</a>)
(<a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/75dc5b1e16944416a287628c50ec4a0cf82c3023">75dc5b1</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/1e512282e9ef7d0392df436e48e237c1900aca9e"><code>1e51228</code></a>
chore(release): v1.16.0 [skip ci]</li>
<li><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/e69abfb5f1b5d3bf993ac2fe66fae85a85af9905"><code>e69abfb</code></a>
feat(logger): add support for <code>AWS_LAMBDA_LOG_LEVEL</code> and
`POWERTOOLS_LOG_LEVE...</li>
<li><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/87fee28e03d7272031e00b2c285c736fd291f37c"><code>87fee28</code></a>
chore: update layer ARN on documentation</li>
<li><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/d508078530fa69b9ab92b203d8a7ccf88e5469a0"><code>d508078</code></a>
chore(release): v1.15.0 [skip ci]</li>
<li><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/6b9b1bcb9baf4b3d8e0e5ec6709594aca09bb033"><code>6b9b1bc</code></a>
feat(maintenance): add support for nodejs20.x runtime (<a
href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1790">#1790</a>)</li>
<li><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/75dc5b1e16944416a287628c50ec4a0cf82c3023"><code>75dc5b1</code></a>
feat(metrics): log directly to stdout (<a
href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1786">#1786</a>)</li>
<li><a
href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/73a56cc61ab3c12faaedf888362136a9dd34a843"><code>73a56cc</code></a>
chore: update layer ARN on documentation</li>
<li>See full diff in <a
href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v1.14.2...v1.16.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@aws-lambda-powertools/tracer&package-manager=npm_and_yarn&previous-version=1.14.2&new-version=1.16.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

Diff for: lambdas/yarn.lock

@@ -92,10 +92,10 @@
     "@aws-sdk/util-utf8-browser" "^3.0.0"
     tslib "^1.11.1"
 
-"@aws-lambda-powertools/commons@^1.14.2":
-  version "1.14.2"
-  resolved "https://registry.yarnpkg.com/@aws-lambda-powertools/commons/-/commons-1.14.2.tgz#930dbf80443afcd7bba1603b79bce416ce2f2b89"
-  integrity sha512-pGW2RSeOEbU1e+mj+MlMkaiM4njO289glFjJA1V+H8bmjvHJXaItroH7lutZ8Gde1Iq+5WoRVQN8M/xmMNSxIA==
+"@aws-lambda-powertools/commons@^1.14.2", "@aws-lambda-powertools/commons@^1.16.0":
+  version "1.16.0"
+  resolved "https://registry.yarnpkg.com/@aws-lambda-powertools/commons/-/commons-1.16.0.tgz#a2388bfda8adadb645119e7e8b7e39db962cef64"
+  integrity sha512-NWCQapc7zbF0dHW469607l16pFIzm6EQNL/uBdY7bDhJ2t98VFpErO7lj0gbqtTtSL28Ev1TMLtP3PYQeq2BLw==
 
 "@aws-lambda-powertools/logger@^1.8.0":
   version "1.14.2"
@@ -106,11 +106,11 @@
     lodash.merge "^4.6.2"
 
 "@aws-lambda-powertools/tracer@^1.14.0":
-  version "1.14.2"
-  resolved "https://registry.yarnpkg.com/@aws-lambda-powertools/tracer/-/tracer-1.14.2.tgz#0ade48674c395f0c07a2cf56c75f5fc33dffa294"
-  integrity sha512-wJqTr7IWQNfVRMpWhn5JFg1Syh9xG+JyqfTsHvQ8USLIzjG5qa5LJKaPVAcugRVN05qzEHYpWKVdrRTEvf663g==
+  version "1.16.0"
+  resolved "https://registry.yarnpkg.com/@aws-lambda-powertools/tracer/-/tracer-1.16.0.tgz#b85fb818445f6a43fecdc6d35f0fe31104e283df"
+  integrity sha512-oJvjSZTvCAb2PDV0yKpAViLgl3aePe2DqCLX0ZWCXGVyoLq7y7KVX5zquDFzntx/LMDA9ZwDQtHYn2hsO9b4dA==
   dependencies:
-    "@aws-lambda-powertools/commons" "^1.14.2"
+    "@aws-lambda-powertools/commons" "^1.16.0"
     aws-xray-sdk-core "^3.5.3"
 
 "@aws-sdk/client-ec2@^3.436.0":