fix(useLogger): remove '<empty string>', allow any args/string substitution

[andretchen0]

Closes #508

Problem

useLogger().logError was logging <empty string> if only one argument was provided.

Solution

Remove the special case for error || '' below. Instead, let console.error handle all the arguments as it does by default.

console.error(`${logPrefix} ${message}`, error || '')

---

Problem

Console string substitution was not working with useLogger().logError and useLogger().logWarning.

Solution

If the first arg is a string, concatenate the logPrefix to the first arg. And allow any type (including strings, numbers) for subsequent args.

Otherwise, avoid coercing the first argument to a string, as this will incorrectly trigger string substitution.

---

Problem

Could not console.error or console.warn any type, or any number of arguments. (E.g., console.warn accepts 1 to n number of arguments, which can be any object, but userLogger().logWarning only accepted 1 string.)

Solution

Type check to enforce at least 1 argument but allow many. Allow any type of argument.

[netlify]

✅ Deploy Preview for tresjs-docs ready!

Name	Link
🔨 Latest commit	541284f
🔍 Latest deploy log	https://app.netlify.com/sites/tresjs-docs/deploys/660832dbc0b32f0009473457
😎 Deploy Preview	https://deploy-preview-510--tresjs-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.