minimal: Simplify syntheticException creation

Whether the error is thrown or not does not matter because stacktraces are generated when `new Error()` is called. In other words: the try-catch in `captureException()` and `captureMessage()` is unnecessary, and we can assign the new `Error` instance directly.

Author: Turbo87

packages/minimal/src/index.ts

@@ -36,12 +36,8 @@ function callOnHub<T>(method: string, ...args: any[]): T {
  */
 // eslint-disable-next-line @typescript-eslint/no-explicit-any, @typescript-eslint/explicit-module-boundary-types
 export function captureException(exception: any, captureContext?: CaptureContext): string {
-  let syntheticException: Error;
-  try {
-    throw new Error('Sentry syntheticException');
-  } catch (exception) {
-    syntheticException = exception as Error;
-  }
+  let syntheticException = new Error('Sentry syntheticException');
+  
   return callOnHub('captureException', exception, {
     captureContext,
     originalException: exception,
@@ -57,12 +53,7 @@ export function captureException(exception: any, captureContext?: CaptureContext
  * @returns The generated eventId.
  */
 export function captureMessage(message: string, captureContext?: CaptureContext | Severity): string {
-  let syntheticException: Error;
-  try {
-    throw new Error(message);
-  } catch (exception) {
-    syntheticException = exception as Error;
-  }
+  let syntheticException = new Error(message);
 
   // This is necessary to provide explicit scopes upgrade, without changing the original
   // arity of the `captureMessage(message, level)` method.