Use upload-artifact@v4 before 30 June 2024

[qinsoon]

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "linux-x86_64-avrora-fastdebug", "linux-x86_64-avrora-release", "linux-x86_64-batik-fastdebug", "linux-x86_64-batik-release", "linux-x86_64-biojava-fastdebug", "linux-x86_64-biojava-release", "linux-x86_64-cassandra-fastdebug", "linux-x86_64-cassandra-release", "linux-x86_64-eclipse-fastdebug", "linux-x86_64-eclipse-release", "linux-x86_64-fop-fastdebug", "linux-x86_64-graphchi-fastdebug", "linux-x86_64-h2-fastdebug", "linux-x86_64-h2o-release", "linux-x86_64-h2-release", "linux-x86_64-jme-fastdebug", "linux-x86_64-jme-release", "linux-x86_64-jython-fastdebug", "linux-x86_64-jython-release", "linux-x86_64-kafka-fastdebug", "linux-x86_64-kafka-release", "linux-x86_64-luindex-fastdebug", "linux-x86_64-luindex-release", "linux-x86_64-lusearch-fastdebug", "linux-x86_64-lusearch-release", "linux-x86_64-pmd-fastdebug", "linux-x86_64-pmd-release", "linux-x86_64-server-fastdebug-bundles-MMTK_EXTREME_ASSERTIONS=1", "linux-x86_64-server-fastdebug-bundles-MMTK_FORWARDING_ON_SIDE=1", "linux-x86_64-server-fastdebug-bundles-MMTK_MALLOC_MARK_SWEEP=1_MMTK_EXTREME_ASSERTIONS=1", "linux-x86_64-server-fastdebug-bundles-MMTK_MALLOC_MARK_SWEEP=1_MMTK_MARK_IN_HEADER=1", "linux-x86_64-server-fastdebug-bundles-MMTK_VO_BIT=1", "linux-x86_64-server-fastdebug-bundles-normal", "linux-x86_64-server-release-bundles-normal", "linux-x86_64-sunflow-release", "linux-x86_64-tomcat-fastdebug", "linux-x86_64-tomcat-release", "linux-x86_64-xalan-release", "linux-x86_64-zxing-fastdebug", "linux-x86_64-zxing-release".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

See https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/.

The deprecation of v3 ..., which is scheduled to take place on June 30, 2024. Version tags will not be removed from the project repositories, however, attempting to use a version of the actions after the deprecation date will result in a workflow failure.