Fix inconsistent mCaps/mTimeOrderedCaps entries

Previously if there was an existing cap, a TimeOrderedCap entry is only inserted in case when there is an inode change. This causes the problem in the short time window when a client might renew the cap that there isn't a timeordered entry and a future expire will never catch this

Closes EOS-4734