Agent info endpoint: do not error out on DB update errors
Recently we had an incident (gitlab-com/gl-infra/production#17655 (closed)) where certain DB table was not writable from the existing code. In the /api/v4/internal/kubernetes/agent_info
we update the last user time for a token when authentication for that token succeeds. If this update fails, the whole authentication call errors out. This update is not that critical, if it fails it should not fail the authentication call. The error should be logged/reported to Sentry, etc, and the call should proceed as normal.
Edited by Mikhail Mazurskiy