[manager] `prismicRepository.pushChanges()` calls `console.error()` when it shouldn't

Versions

@slicemachine/manager: 0.2.2
node: 18.12.1

Reproduction

import { createSliceMachineManager } from "@slicemachine/manager";

const model = {
  id: "foo",
  label: "foo",
  repeatable: false,
  status: true,
  json: {
    Main: {},
  },
};

const manager = createSliceMachineManager();

(async () => {
  try {
    await manager.prismicRepository.pushChanges({
      changes: [
        {
          type: "CustomType",
          id: model.id,
          status: "NEW",
        },
      ],
      confirmDeleteDocuments: false,
    });

    await manager.prismicRepository.pushChanges({
      changes: [
        {
          type: "CustomType",
          id: model.id,
          status: "NEW",
        },
      ],
      confirmDeleteDocuments: false,
    });
  } finally {
    // Only included to clean up the previous changes.

    await manager.prismicRepository.pushChanges({
      changes: [
        {
          type: "CustomType",
          id: model.id,
          status: "DELETED",
        },
      ],
      confirmDeleteDocuments: false,
    });
  }
})();

Steps to reproduce

Log in to Prismic: npx prismic-cli@latest login
Run the above script in a project with a valid slicemachine.config.json.

It pushes a custom type model with the NEW status twice. The second call should trigger an API error which gets logged to the console.

What is expected?

The second manager.prismicRepository.pushChanges() call should throw an error, but it should not log to the console.

What is actually happening?

manager.prismicRepository.pushChanges() calls console.error() when it encounters an API error.

See these lines: https://github.com/prismicio/slice-machine/blob/b4d46f012cba0f46383e38a368eb419de667326b/packages/manager/src/managers/prismicRepository/PrismicRepositoryManager.ts#L404-L409

Logging and handling errors should be the job of the consumer, not @prismicio/manager.

In my specific case, I want to catch the error and try a different status. However, the console.error() signals to the user that something went wrong, despite this being an expected state.

prismicio / slice-machine