Avoid rebuilding cache when the primary model has been destroyed

[praveenram]

Summary

Restrict the queueing of RefillJob to only happen on create and update events, avoid queueing the job on destroy.

Thermos uses globalid serialization for the ActiveJob params when available, to serialize the self instance variable to the queue backend, which is then automatically deserialized by Rails / ActiveJob, reference.

For any records that were destroyed, the serialization will happen without an issue with the in-memory instance of the model, but during deserialization by the background job worker, the record will not be available causing the RefillJob to fail.

Potential Improvement:

• Instead of avoiding queueing the job, we can also clear any existing data from cache from the record.

[athal7]

Looks great thanks @praveenram !