chore: remove device_info_plus and add quill_native_bridge to access platform specific APIs

[EchoEllet]

Description

Remove device_info_plus and create a quill_native_bridge plugin for accessing platform-specific APIs

Currently, we have device_info_plus as a dependency to fix a bug on iOS simulator (See #652) by check if the device is an iOS simulator, removing the plugin and add quill_native_bridge which currently can only check if the platform is iOS simulator, we might expand it in the future since we need platform-specific APIs in some areas such as accessing the clipboard and spell checker system service.

This PR doesn't make flutter_quill a plugin, instead, it creates a new plugin and requires it as a dependency in flutter_quill.

Moving packages into their own directory

We might consider moving the packages into their own directory (packages) however there are some places that need to be manually updated first:

1. The scripts
2. The CI and the Automated publishing by GitHub
3. The reference of the flutter_quill in the other packages (like flutter_quill_extensions)
4. The markdown files like README.md or CHANGELOG.md and all the other docs files in the project should update the links
5. There are other files such as quill_native_bridge/ios/quill_native_bridge.podspec

We will discuss it in a different issue later.

Related Issues

• Fix #1833
• Related #1783
• Related #1019
• Related #652
• Related #1216
• Related #1253

Type of Change

• [x] ✨ New feature: Adds new functionality without breaking existing features.
• [ ] 🛠️ Bug fix: Resolves an issue without altering current behavior.
• [ ] 🧹 Code refactor: Code restructuring that does not affect behavior.
• [ ] ❌ Breaking change: Alters existing functionality and requires updates.
• [ ] 🧪 Tests: Adds new tests or modifies existing tests.
• [ ] 📝 Documentation: Updates or additions to documentation.
• [x] 🗑️ Chore: Routine tasks, or maintenance.
• [ ] ✅ Build configuration change: Changes to build or deploy processes.

[EchoEllet]

If you have suggestions or thoughts regarding this PR, I'm open to hearing them.

For the plugin name, I would go for quill_platform_bridge or quill_native_bridge.

• I choose to remove the flutter_ prefix from the plugin name to make it a bit shorter.
• I didn't choose quill_plugin since it might not be clear that it's a platform plugin for accessing platform API.