(android) fix: use provider prefix to avoid conflict with cordova-open plugin

[LoicEvenium]

Platforms affected

cordova-android

Motivation and Context

Application crash when open the camera if cordova-plugin-open installed.
Providers of cordova-plugin-open and cordova-plugin-camera are in conflicts using the same android:authorities value. See the AndroidManifest:

    <provider android:authorities="${applicationId}.provider" android:exported="false" android:grantUriPermissions="true" android:name="org.apache.cordova.camera.FileProvider">
      <meta-data android:name="android.support.FILE_PROVIDER_PATHS" android:resource="@xml/camera_provider_paths"/>
    </provider>
    <provider android:authorities="${applicationId}.provider" android:exported="false" android:grantUriPermissions="true" android:name="androidx.core.content.FileProvider">
      <meta-data android:name="android.support.FILE_PROVIDER_PATHS" android:resource="@xml/provider_paths"/>
    </provider>

Fix: #416

Description

Add "camera" in the android:authorities to void namespace conflict

Testing

Open camera, take a picture

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

[pseudooriginal]

Can this PR be merged please? It brakes the plugin on all Android devices.

[breautek]

Overall this looks good, just a few minor things I would change to avoid using general keywords that other libraries/plugins may also end up using.

[pseudooriginal]

Thank you for your speed 😊

[breautek]

Thanks for your contribution, it looks good to me. I'd like to have at least one other positive vote by another PMC member before I merge.

[netzzeit]

Is there any chance this change is being merged soon? :)

[timbru31]

There is still an open discussion. I'm not merging something that I'm not 100% sure of that it does not cause a breaking change - unless it's explicitly stated so.

[jcesarmobile]

looks good to me