[os-qfeeds-connector] - 'Updated' field in widget not updated at successful pull

[Q-Feeds]

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• The title contains the plugin to which this issue belongs

Describe the bug
The 'Updated' field in the widget showed the wrong timestamp. This happend because the index was fetched before the update ran (to check if there's an update available). But the index was not pulled again after the fetch.

To Reproduce
Setup Q-Feeds and wait for next update to see the updated field is not being updated while the pull was successful.

Expected behavior
Updated field shows latest successful pull timestamp

Additional context
I personally prefer to update the field based on the timestamp of the local file instead of doing an extra API call to the licenses endpoint.

Environment
n/a

[AdSchellevis]

currently a fetch_index is followed by a fetch in qfeedsctl.py, but I would assume the chance is rather small the updated_at stamp is changed between those two actions, unless the stamp is changed by the fetch on our end. Is that the case or am I missing something here?

[Q-Feeds]

That's the case indeed updated at on our end is based on the last pull. So the fetch_index is always running exactly 1 cadence behind. If we update this timestamp locally based on the file change timestamp it will always be accurate.

[AdSchellevis]

ok, so you need another index fetch after pulling the data to be consistent with upstream modification stamp, right?

[Q-Feeds]

Thank you!!