fix(types): improve type extraction for namespaced responses and correct async iterator types

[wolfy1339]

The iterator() function returns an object containing a key of Symbol.asyncIterator, which is an object with a next() function. Only the top-level has the Symbol.asyncIterator, and the next() function is not present at the top-level

The GetResultsType<T> sometimes doesn't return the paginated data and returns the whole data object. For some reason TypeScript sometimes get's confused and returns all the keys in the object in the call KnownKeysMatching<T["data"], any[]>
In order to remedy that, we remove keys that we know do not contain the data ("repository_selection" | "total_count" | "incomplete_results") and we then always get the data.

The NormalizeResponse<T> type would return the intersection of the original data from the request and the paginated data. To remedy that, we use Omit<T, K> to remove the data from the request data and only return the paginated data instead.

Resolves #350

---

Before the change?

• Contained wrong types for the return value regarding AsyncIterator
• The GetResultsType<T> wouldn't always get the key with the data

After the change?

• Corrects the types for AsyncIterator vs AsyncIterableIterator
• The GetResultsType<T> correctly gets the pagination data

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No
  While not strictly a breaking change, it can cause breakage to end users as the types have changed.

---

[github-actions]

🎉 This PR is included in version 11.3.5 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀