fix(connection): avoid calling connection.close() internally with force: Object

[vkarpov15]

Fix #15531

Summary

The crux of #15531 is that we're setting force to an object when connection.close() expects force to be a boolean.

Examples

[Copilot]

Pull Request Overview

This pull request fixes issue #15531 by correcting the type of the force parameter when calling connection.close() internally. The issue was that an object was being passed as the force parameter when the method expects a boolean value.

• Extracts the boolean force value from an object parameter before passing it to internal close() and destroy() calls
• Adds a test case to verify the fix works correctly with useDb() method

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
lib/connection.js	Adds logic to extract boolean force value from object parameter in onClose() method
test/connection.test.js	Adds regression test for reopening connection after close with useDb()

Comments suppressed due to low confidence (1)

lib/connection.js:1327

• [nitpick] The variable name wasForceClosed is misleading as it suggests a past state, but it's actually extracting the current force value. Consider renaming to forceValue or forceBool to better reflect its purpose.

  const wasForceClosed = typeof force === 'object' && force !== null ? force.force : force;