Bug: Error thrown of setting a property name that only has a getter

[auguwu]

Describe the bug
In some applications, ts-log will report the error (this is with ts-node, same errors produces in normal JavaScript!):

 TypeError  Cannot set property name of  which has only a getter
error stack:
• LoggerWithoutCallSite.ts:463 _buildErrorObject
    node_modules\tslog\src\LoggerWithoutCallSite.ts:463:21

• LoggerWithoutCallSite.ts:424 <anonymous>
    node_modules\tslog\src\LoggerWithoutCallSite.ts:424:16

• LoggerWithoutCallSite.ts:421 _buildLogObject
    node_modules\tslog\src\LoggerWithoutCallSite.ts:421:28

• LoggerWithoutCallSite.ts:332 _handleLog
    node_modules\tslog\src\LoggerWithoutCallSite.ts:332:40

• LoggerWithoutCallSite.ts:289 fatal
    node_modules\tslog\src\LoggerWithoutCallSite.ts:289:28

• main.ts:54 <anonymous>
    main.ts:54:60

• node:events:327 emit
    node:events:327:20

• node:domain:486 EventEmitter.emit
    node:domain:486:12

• source-map-support.js:495 process.emit
    C:\Users\<name>\AppData\Roaming\npm\node_modules\ts-node\node_modules\source-map-support\source-map-support.js:495:21

To Reproduce
This happens when you do:

const { Logger } = require('tslog');
const logger = new Logger();

class CustomError extends Error {
  get name() {
    return 'CustomError';
  }
}

try {
  throw new CustomError();
} catch(ex) {
  logger.fatal(ex);
  // logger.error(ex); also causes it!
}

Expected behavior
Shouldn't override setters (it seems?) and the error should be printed.

Node.js Version
v15.0.1

OS incl. Version
Windows 10 Pro (build 2004, 10.0.19041)