fix(android): hasWritePermission for SDK 33

[erisu]

Platforms affected

android

Motivation and Context

rebase, fix, and simplify changes from #581

Closes #581

Description

This PR performed following changes against #581:

• Rebased against current main branch
• Reverted previous changes to getWritePermission but applied suggestion to simplify. the condition check and to add extra accidental calls, even though the method would never be called in that scenario.
• Simplifed hasWritePermission logic
• Added comment suggestion to hasWritePermission

Testing

build test

Checklist

• I've run the tests to see all new and existing tests pass
• I added automated test coverage as appropriate for this change
• Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
• If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
• I've updated the documentation if necessary

[ath0mas]

What is happening here in the else case?
Mostly asking because getWritePermission is always called providing a callbackContext.
Are we sure it does not wait indefinitely?
Is doing nothing really fine, or should callbackContext be called in every case, to guarantee the execution flow continues?

[ath0mas]

I think I "found" my own answer:
in current code, in the case of Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU, getWritePermission is never called ...
So my question does not really mater, even if strictly speaking it is probably a problem for the execution flow, indefinitely waiting for the callbackContext.

Details:
getWritePermission calls are always preceded by a check for needPermission(nativeURL, WRITE), that will return false in this same given versions condition, because hasWritePermission was changed to always return true for it.
So, the if (android.os.Build.VERSION.SDK_INT < Build.VERSION_CODES.TIRAMISU) { added in getWritePermission is mostly useless, and should whether be removed or be fixed.