`@sapui5/ts-types-esm` - `opaQunit` should be an overload & `async` option should be optional

declare module "sap/ui/test/opaQunit" {
  export default function opaQunit(
    /**
     * name of the QUnit test.
     */
    testName: string,
    /**
     * integer value only supported in QUnit v1.x: denotes how many assertions are expected to be made in the
     * test. If a function is passed instead, it is considered to be the callback parameter
     */
    expected: int | Function,
    /**
     * the test function. Expects 3 arguments, in order: {@link sap.ui.test.Opa.config}.arrangements, {@link
     * sap.ui.test.Opa.config}.actions, {@link sap.ui.test.Opa.config}.assertions. These arguments will be prefilled
     * by OPA
     */
    callback: Function,
    /**
     * available only in QUnit v1.x. Indicates whether the test is asynchronous. False by default.
     */
    async: boolean
  ): void;
}

if that documentation is correct, the definition should instead be something like:

declare module 'sap/ui/test/opaQunit' {
    export default function opaQunit(
        testName: string,
        expected: int,
        callback: Function,
        async?: boolean,
    ): void
    export default function opaQunit(testName: string, callback: Function, async?: boolean): void
}

(assuming async becomes the third argument if a callback is provided as the second, i'm not sure how the impl handles it)

Locate the declaration for the sap/ui/test/opaQunit module and compare its signature with the documented argument forms in the issue. Confirm how the implementation handles async when the callback is the second argument, then update the overloads and verify the generated TypeScript definitions if repository checks are available.