fix: Enable Browser Debug when using project configurations

[Alanoll]

This fixes (at least in my use cases) #691 .

The core problem appears to be how the extension attempts to enable the browser inspector via the configureVitest hook of the inline plugin. The hook doesn't execute when Vitest uses project configurations (so maybe an underlying bug in Vitest itself?), and therefore the inspector options aren't enabled.

I split the hook method logic into two places:

• The inspector options are now passed as CLI options to Vitest since they're are passed down into the per project config resolution logic
• The setupFiles are now updated in the reporter's onInit
  • This appears to be too late for inspector options to be honored (at least in my brief testing), which is why I stuck with the CLI method

Fixes #691