Composter deletes its item even if it wasn't taken

Place a hopper and fill every slot with 1 stackable item (eg: stone). In this configuration, the hopper cannot accept any new items.
Place a composter on top. Fill the composter up (eg: with pumpkin pie).

Expected result:
The filled composter turns into bone meal that cannot be pulled by the hopper and thus should stay in the composter.
Actual result:
The bonemeal gets deleted by the hopper.

Checking the code and the fix seems simple : This occurs because the hopper first removes the item from the container, tries to insert it in any of his slots, and insert the remainder back into the original container (HopperBlockEntity.tryTakeInItemFromSlot()).
While this logic works for any other container, it doesn’t work with ComposterBlock.OutputContainer because when the hopper puts back the remaining ItemStack into the container via SimpleContainer.setItem(), and setItem() calls this.setChanged() which ComposterBlock.OutputContainer overrides to unconditionally call ComposterBlock.empty() → deleting the bonemeal.

The fix is quite simple, and would simply require wrapping the logic in ComposterBlock.OutputContainer.setChanged() with a if (this.isEmpty()) :

		@Override
		public void setChanged() {
		    if (this.isEmpty()) {
			    ComposterBlock.empty(null, this.state, this.level, this.pos);
			    this.changed = true;
			}
		}