Refactor function loadLibraryFromJar in NativeUtils.java

[Muhanned-Anwar]

he main changes are:

Extracted the resource copying logic to a separate method copyResourceToFile.
Renamed the temp variable to tempFile to make its purpose clearer.
Simplified the method by removing unnecessary comments.
Used try-with-resources for the input stream instead of a try-catch block.
Changed the catch block for the NullPointerException to throw a FileNotFoundException instead of catching it and rethrowing.

[HadetTheUndying]

It looks like you're using the GItHub Desktop app. can you please modify your PRs to have more descriptive Titles and your commit messages to be more specific. I don't work for Twitter but from the PR page it looks like you've opened the same PR five times now when that's clearly not the case. But at a glance it looks like you're spamming, when you're clearly not.

[Muhanned-Anwar]

It looks like you're using the GItHub Desktop app. can you please modify your PRs to have more descriptive Titles and your commit messages to be more specific. I don't work for Twitter but from the PR page it looks like you've opened the same PR five times now when that's clearly not the case. But at a glance it looks like you're spamming, when you're clearly not.

A more explanation of the modifications has been added

[uwussimo]

The updated code appears to be well-written and concise. However, a couple of minor improvements could be made:

The method name loadLibraryFromJar might not accurately reflect what the method does. The method's name suggests that it loads a library from a JAR, but in reality, it copies a resource from a JAR to a file and then loads the file as a library. Therefore, it might be better to rename the method to something like copyResourceToLibrary to better reflect its functionality.

The IOException thrown in the finally block when deleting the temporary file could mask any exceptions thrown during the System.load call. To avoid this, it might be better to catch and handle any exceptions thrown during the System.load call explicitly, rather than relying on the finally block.

These are minor suggestions, and the updated code is already well-written and efficient. Therefore, they are not critical, and the code is recommended to be approved as is.