Is there a programmatic way to force a service to have its entry and characteristics updated/refreshed?
### Current Situation

Hello!

I'm working on the homebridge-sensibo-ac plugin and have come across one scenario (currently) where, I think, it might be good to 'refresh' the Homebridge and Home app's instance of a service (and/or accessory).

In the, admittedly somewhat rare, situation that a user decides that they want to remove the verticalSwing (Oscillate) button, defined by the SwingMode characteristic, on their HeaterCooler service the code calls removeCharacteristic. However, even after restarting Homebridge, unfortunately the Oscillate button is still shown there in the Home iOS app.

Am I doing something wrong?

Looking at the cachedAccessories file I can see that the SwingMode characteristic is still defined under the HeaterCooler services characteristics array (as well as being in the optionalCharacteristics array). So I'm wondering if there is a way to force an update, and also update the cache, in case that is contributing?

Do I need to remove (or unpublished) the respective Service [or the whole accessory?] and then re-add (or publish) it?

I did see #552, and I'm aware that users could remove the accessory from the cache manually, but wanted to check if that really is the only/best way (as it's not a great user experience). Especially as, based on my understanding, that would then require any automations etc to be re-configured (could be wrong about this).

### Logs

```markdown
[05/01/2023, 9:27:50 pm] [SensiboAC] Removing Vertical Swing (Oscillate) button

Actual code called:
this.HeaterCoolerService.removeCharacteristic(Characteristic.SwingMode)
```


### Configuration

```json
I don't believe that this is relevant, but can provide if it would help.
```


### Environment

- OS: RaspberryPi (also tried on Mac OS)
- Homebridge: 1.6.0
- homebridge-config-ui-x: v4.50.2
- Node: 16.19.0 on the RPi (19.3.0 on the Mac)
- npm: 8.19.3 on the RPi (9.2.0 on the Mac)


### Process Supervisor

hb-service

### Additional Context

_No response_