fix: handle expired refs

[WYGIN]

Types of changes

• Chore (a non-breaking change which is related to package maintenance)
• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

• moving res related code that processes response and either returns a res or throws an error are moved to a private function for reusability
• created a logic that will treat Non-Master Refs as explicitly defined refs
  • 1. and returns an 410 error after several retries to us
  • 2. returns 200 status code if response is successful

Checklist:

• My change requires an update to the official documentation.
• All TSDoc comments are up-to-date and new ones have been added where necessary.
• All new and existing tests are passing.

Resolves:

resolves: #333

[WYGIN]

@angeloashmore can you please take a look at this pr and let me know if any changes required

[stephanebachelier]

@angeloashmore Could you take a look at this PR? This seems interesting as there are multiple comments in the community forums about this annoying bug.