fix(salud): use exponential backoff for wake up of salud check

[gacevicljubisa]

Checklist

• I have read the coding guide.
• My change requires a documentation update, and I have done it.
• I have added tests to cover my changes.
• I have filled out the description and linked the related issues.

Description

Idea is to reduce the time that salud spends to update the peer status. This will help the light node spin time and readiness.

Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

[martinconic]

Please can you explain more on how this helps light nodes spin time and readiness and if there are other benefits from these changes? In the end after exponential backoff reaches 5 minutes, it will stay at 5 minutes as it is now.

[gacevicljubisa]

Please can you explain more on how this helps light nodes spin time and readiness and if there are other benefits from these changes? In the end after exponential backoff reaches 5 minutes, it will stay at 5 minutes as it is now.

Salud has own wakup time and it is hardcoded to 5 minutes. In the first run it can not find any peers. Beacuse of that, node needs to wait next run to be responsive. Idea for the expontial Backoff is to reduce the wait time. And later continue working on every 5 minutes.