If you do not have data of old satellites, then you do not need to run the forget satellite command. You also do not need to forget the Saltlake satellite. If you want to leave this satellite, you may call a Graceful Exit on it: Graceful Exit Guide (new procedure as of 2023-10-?)
The garbage should be moved by the retain process to the trash and deleted 7 days later.
When your node did receive a BF from the Saltlake satellite last time?
I didn’t find records from it in your logs excerpt.
docker logs storagenode 2>&1 | grep "retain" | grep "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE" | tail
I have a suspicion: since the Saltlake satellite is sure that your node doesn’t have any data (it’s literally zero accordingly your graphs and the fact that other nodes in the network received at least one correct report from this satellite), and also amount of audits doesn’t change for days accordingly your logs, I can guess that the satellite do not issue the BF too, because it should contain pieces, which your node should keep. But since there shouldn’t be any pieces accordingly its databases, it doesn’t generate a BF…
In that case you need to receive something from that satellite, to allow it to generate a BF. But it cannot, because it’s full even with overusage… You need to have a free space to allow the node to receive something from the Saltlake satellite.
I can only offer to remove all files from the temp folder. If there is nothing, the next suggestion is to perform an extremely dangerous action - try to remove pieces from one of the subfolders in the blobs folder for that satellite (see Satellite info (Address, ID, Blobs folder, Hex)) and restart the node to allow it to have a free space. Then maybe something will arrive from the Saltlake satellite and then wait when it would send the next BF.