upgrade actions/core to version 3v4.0.3v4

The relevant changes are in clean.js/restore.js. I'm very, very far away
from the entire Javascript infrastructure, and absolutely don't
understand why this changes were necessary. Thanks, ChatGPT! Supposedly,
this has something to do with the actions/core's transition to ESM or
whatever.

1 files changed, 2 insertions, 6 deletions

diff --git a/node_modules/@actions/core/lib/utils.js b/node_modules/@actions/core/lib/utils.js
index a95a3bb..37d0ee5 100644
--- a/node_modules/@actions/core/lib/utils.js
+++ b/node_modules/@actions/core/lib/utils.js
@@ -1,14 +1,10 @@
-"use strict";
 // We use any as a valid input type
 /* eslint-disable @typescript-eslint/no-explicit-any */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.toCommandValue = toCommandValue;
-exports.toCommandProperties = toCommandProperties;
 /**
  * Sanitizes an input into a string so it can be passed into issueCommand safely
  * @param input input to sanitize into a string
  */
-function toCommandValue(input) {
+export function toCommandValue(input) {
     if (input === null || input === undefined) {
         return '';
     }
@@ -23,7 +19,7 @@ function toCommandValue(input) {
  * @returns The command properties to send with the actual annotation command
  * See IssueCommandProperties: https://github.com/actions/runner/blob/main/src/Runner.Worker/ActionCommandManager.cs#L646
  */
-function toCommandProperties(annotationProperties) {
+export function toCommandProperties(annotationProperties) {
     if (!Object.keys(annotationProperties).length) {
         return {};
     }