feat: add fromiter to numpy frontend

[nwanne56]

PR Description

Related Issue

Close #22814

Checklist

• Did you add a function?
• Did you add the tests?
• Did you follow the steps we provided?

Socials:

[github-actions]

Thanks for contributing to Ivy! 😊👏
Here are some of the important points from our Contributing Guidelines 📝:
1. Feel free to ignore the run_tests (1), run_tests (2), … jobs, and only look at the display_test_results job. 👀 It contains the following two sections:
- Combined Test Results: This shows the results of all the ivy tests that ran on the PR. ✔️
- New Failures Introduced: This lists the tests that are passing on main, but fail on the PR Fork. Please try to make sure that there are no such tests. 💪
2. The lint / Check formatting / check-formatting tests check for the formatting of your code. 📜 If it fails, please check the exact error message in the logs and fix the same. ⚠️🔧
3. Finally, the test-docstrings / run-docstring-tests check for the changes made in docstrings of the functions. This may be skipped, as well. 📚
Happy coding! 🎉👨‍💻

[Daniel4078]

Hello, your tests are currently all failing for the same error:
E TypeError: fromiter() got an unexpected keyword argument 'iterable'
Please read the comments below

[Daniel4078]

Please update your test by using helpers.dtype_and_values to generate the iter argument as your current method will cause the following error when it generate a massive value:
E OverflowError: Python int too large to convert to C long
Read this(https://unify.ai/docs/ivy/overview/deep_dive/ivy_frontends_tests.html) for more details.

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Protected Branch

In order to be considered for merging, the pull request changes must not be implemented on the "main" branch. This is described in our Contributing Guide. We are closing this pull request and we would suggest that you implement your changes as described in our Contributing Guide and open a new pull request.

[Daniel4078]

Please try to copy the changes you have made to a new branch in your repo as it is not a good practice to merge from your main to ivy main. In addition, there are some major changes applied to the code base recently, so take this as a chance to update your repo as well. Thanks.

[github-actions]

Thank you for this PR, here is the CI results:

---

This pull request does not result in any additional test failures. Congratulations!