multiCapabilities behavior with directConnect after upgrading to Protractor 7.0.0

Goal: achieve reliable parallel test execution across multiple browser instances using multiCapabilities when directConnect is enabled after migrating to Protractor 7.0.0 configuration format.

Constraints: the upgrade deprecated seleniumAddress, seleniumPort, and jsonPath, requiring a capabilities block; directConnect bypasses the Selenium Server, so any custom grid settings must be defined within capabilities. Documentation does not clarify how multiple capabilities are handled under directConnect, leading to inconsistent test counts and reporting across CI environments.

Questions: Does Protractor 7.0.0 launch a separate ChromeDriver instance for each entry in multiCapabilities when directConnect is true? Are the capabilities merged or overridden? How can one verify that each capability set is applied to the intended browser instance?