Fix Oauth token refresh & Quarkus Log exception

[SravanThotakura05]

@ozangunalp - To validate the OAuth token refresh issue, i have left the extension to run since morning and i haven't seen the issue of disconnection. Integration test is not added as we were seeing this issue after few hours.

My observation during testing.

1. Buffer overflow - Ideally this will not occur in real use as user need to set the interval so that only one request is made before token expiry. If they are setting smaller intervals then buffer might overflow due to large number of requests.
2. Solace Reconnection - Reconnection might happen on idle connections depending on keep alive configuration. To avoid unauthorised token we are updating the token based on Solace Reconnect Listener interface.
3. Removed the filter cause in Token refresh method and updated the call method as it already has if condition check.

On Quarkus Log exception since we were not able to reproduce I have added empty beans.xml as recommended by you

[ozangunalp]

All this looks good.

For the overflow issue, I think this can happen when the token refresh takes too much time. Normally, it should not surpass the HTTP connection timeout. As a safeguard, we may add a onOverflow().drop() to the tick and add a timeout after token refresh calls .ifNoItem().after(some duration).fail()

For the log issue, let's see if the beans.xml resolves the problem, otherwise, we can fall back to using the normal logger and report the issue to the Quarkus repo.

[SravanThotakura05]

@ozangunalp - Added new property to configure refresh timeout for the requests and fail on no response.

Commit - 0995bc0