[Proposal] Camera-only alternative to PixImagePicker (no storage permission required)

[davidcrespo99]

Is your feature request related to a problem? Please describe.
Yes. In some projects, it is no longer possible to request image read permissions from Google because the usage frequency is too low to justify the permission according to Play Store policies. However, I still want to use the camera functionality provided by PixImagePicker. The current library is designed to handle both image picking from storage and the camera, which means it still requires storage permissions.

Describe the solution you'd like
I have created a simplified, camera-only version of the library that removes any functionality requiring storage read permissions. This allows integration of PixImagePicker in projects that must comply with Google Play restrictions while still enabling users to take photos. My proposal is to host this as an alternative branch (e.g., camera-only) so developers can choose between the full feature set and the lightweight camera-only version without affecting the current main branch.

Describe alternatives you've considered

• Maintaining a separate fork of PixImagePicker with the stripped-down camera implementation (but this would duplicate maintenance efforts).

• Adding runtime flags to the existing library to disable storage features (but this adds complexity to the core library and increases maintenance overhead).

Additional context
This variant keeps the same coding style and structure as PixImagePicker but removes all gallery/image-picking code.

Intended for scenarios where:

• Gallery selection is not required.
• Google Play policy restricts requesting storage permissions.
• Simpler integration and smaller footprint are desired.

Example use cases: secure apps, restricted-permission environments, or one-time-photo workflows.