fix: Simplified level assignment logic in BrowserConsole

[brawncode]

Description

I’ve updated the logic in the BrowserConsole function that handles the level property. Previously, there was a redundant check for opts in the conditional expression. Since we are already checking for the existence of opts?.level, it's unnecessary to verify opts again.

I’ve simplified the assignment to use the nullish coalescing operator (??), which directly assigns the value of opts.level if it exists, or defaults to "info" if it doesn't ;)

[CLAassistant]

All committers have signed the CLA.

[matthewkeil]

Thanks for you submission @brawncode !!! We love outside contributions and welcome you to attempt another PR. This is unfortunately something we cannot merge. The code does not achieve the goal that you think it will. Please feel free to reach out to us over discord if you have any questions, concerns or would like to take another shot at this! Thanks again!!

[wemeetagain]

Just to clarify, the Object.prototype.hasOwnProperty.call(this.levels, opts.level) is ensuring that the opt.level is one of "error", "warn", "info", "verbose", "debug", "trace" so removing that part removes that validation/coercion.