fix: isolate google-chrome-stable package removal to prevent skipping other packages

[jim60105]

Problem Description

In Ubuntu 24.04 LTS Arm environments, the google-chrome-stable package does not exist, which causes the entire apt-get remove command containing this package to fail, thereby skipping the removal of other packages.

As shown in the error log from issue #41:

Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package google-chrome-stable
Warning: The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...

Solution

This PR isolates google-chrome-stable from the multi-package removal command, following the same approach used for google-cloud-sdk and google-cloud-cli.

Changes Made

1. Remove google-chrome-stable from the multi-package command:

   # Before
   sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing
   
   # After  
   sudo apt-get remove -y azure-cli firefox powershell mono-devel libgl1-mesa-dri --fix-missing

2. Add individual google-chrome-stable removal command:

   sudo apt-get remove -y google-chrome-stable --fix-missing || echo "::debug::The command [sudo apt-get remove -y google-chrome-stable --fix-missing] failed to complete successfully. Proceeding..."

Benefits

• ✅ Prevents single package failures from affecting other package removals
• ✅ Uses ::debug:: level error handling, consistent with other Google packages
• ✅ Maintains backward compatibility
• ✅ Improves stability across different Ubuntu versions and architectures

Testing

The modified code has correct YAML syntax and follows the same logic as existing google-cloud-sdk and google-cloud-cli handling.

Related Issue

Resolves #41

[hjmjohnson]

@jim60105

A different change that circumvents the problem is introduced in

I have forked and incorporated many of the recommended fixes in various forks into a new repo:

git@github.com:BRAINSia/free-disk-space.git

uses: BRAINSia/free-disk-space@v2

[jim60105]

Hi @hjmjohnson, thanks for the fork you provided!

Your version handles google-chrome-stable in a similar way, and I think it will fail with the same error.
The main problem is that the Arm image itself does not have google-chrome-stable package. See #41
https://github.com/BRAINSia/free-disk-space/blob/bf53006decae0ca603555a3943be99d58b4797bc/action.yml#L264-L273