[WIP] [Core] Token refresh via error

[No0b1t0]

• refresh token when invalid for pagerduty, support retry transport with custom method, async only, with tests
• now support return to basic retry handeling when config file is not provided, with test

Description

What -
This PR holds within the scheduled refresh from the #1254 PR, this is a merge that also adds functionality for a custom retry invoked by the integration itself.
Why -
Instead of loading the configuration only on pod start, we aim to be able to periodically load the configuration and / or to load the details when we encounter an authentication error.
How -
This PR introduces an abstract class for Integration retry strategy and for refresh handling, while we aim to move the refresh
please note that the refresh from file was moved to the utils file at the core project, this way the integration will only ask to refresh the token without any consideration on how it is being implemented

tests were added as well

see additional details at task notion page: https://www.notion.so/Refresh-integration-configuration-from-file-part-A-1739be8ff7e380d5bcf7fd2442093f15?pvs=4

Type of change

Please leave one option from the following and delete the rest:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New Integration (non-breaking change which adds a new integration)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Non-breaking change (fix of existing functionality that will not change current behavior)
• Documentation (added/updated documentation)