Correct clientReady hook in Auto Poll mode

[adams85]

Describe the purpose of your pull request

So far the clientReady event has fired in Auto Poll mode only when receiving 200, 304, 403 or 404 status code. In other cases (including the case of network errors) maxInitWaitTime has been waited before firing clientReady.

Breaking changes:

• Change the behavior of the clientReady hook to fire after the completion of the first fetch operation in Auto Poll mode - regardless of success or failure - to make the behavior consistent with other SDKs.

Requirement checklist (only if applicable)

• I have covered the applied changes with automated tests.
• I have executed the full automated test set against my changes.
• I have validated my changes against all supported platform versions.
• I have read and accepted the contribution agreement.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3687e95) 91.63% compared to head (5bd8ce6) 91.75%.
Report is 2 commits behind head on master.

❗ Current head 5bd8ce6 differs from pull request most recent head d5d2b55. Consider uploading reports for the commit d5d2b55 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #94      +/-   ##
==========================================
+ Coverage   91.63%   91.75%   +0.12%     
==========================================
  Files          18       18              
  Lines        1613     1613              
  Branches      406      408       +2     
==========================================
+ Hits         1478     1480       +2     
+ Misses        134      132       -2     
  Partials        1        1              

Files	Coverage Δ
src/AutoPollConfigService.ts	96.77% <100.00%> (-0.04%)	⬇️
src/ConfigServiceBase.ts	89.93% <100.00%> (+0.69%)	⬆️

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication