fix(metrics): captureColdStartMetric and throwOnEmptyMetrics when set to false was interpreted as true

[flochaz]

Description of your changes

Metrics' Middy implementation was checking for undefined to evaluate throwOnEmptyMetrics and captureColdStartMetrics.

How to verify this change

1. Get only the unit tests from this PR, see them fail
2. Get the update on middy.ts
3. rerun the unit tests and see them passed

Related issues, RFCs

Issue number: #1088

PR status

Is this ready for review?: YES
Is it a breaking change?: NO

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding changes to the examples
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• Any dependent changes have been merged and published in downstream module
• The PR title follows the conventional commit semantics

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

No related issues found. Please ensure there is an open issue related to this change to avoid significant delays or closure.

[dreamorosi]

Thanks for the fix!