WIP Package info

[todi1856]

This pull request introduces a new feature to the Android Logcat tool, adding support for package information management. The changes include new menu options, new classes, and methods to handle package operations such as launching, pausing, stopping, and uninstalling packages.

New Feature: Package Information Management

• com.unity.mobile.android-logcat/Editor/AndroidLogcatConsoleWindow.cs: Added a new menu option for "Package Information" in the tools context menu and its handling logic. [1] [2]
• com.unity.mobile.android-logcat/Editor/AndroidLogcatContextMenu.cs: Introduced a new enum value PackageInformation in ToolsContextMenu.
• com.unity.mobile.android-logcat/Editor/AndroidLogcatPackageEntry.cs: Created a new class PackageEntry with methods to launch, pause, stop, and uninstall packages.
• com.unity.mobile.android-logcat/Editor/AndroidLogcatPackagesWindow.cs: Implemented a new window AndroidLogcatPackagesWindow to display and manage package information.
• com.unity.mobile.android-logcat/Editor/AndroidLogcatUtilities.cs: Added methods to retrieve package lists and properties from devices and to uninstall packages with confirmation. [1] [2]

User Settings Enhancements

• com.unity.mobile.android-logcat/Editor/AndroidLogcatUserSettings.cs: Added new settings for package properties filtering. [1] [2] [3]

Meta Files

• com.unity.mobile.android-logcat/Editor/AndroidLogcatPackageEntry.cs.meta: Added meta file for AndroidLogcatPackageEntry.cs.
• com.unity.mobile.android-logcat/Editor/AndroidLogcatPackagesWindow.cs.meta: Added meta file for AndroidLogcatPackagesWindow.cs.[Copilot is generating a summary...]## Please read and consider what information you want to pass on to people reviewing this PR

Purpose of PR

Type of change:

• Bug fix
• New feature
• Code refactor
• Breaking change
• Documentation update
• Other (please describe)

• Description of the feature
  What it does, why was it created, how does it work and so on...
• Links to screenshots, design docs, user docs, etc.
• Links to Jira/Fogbugz cases
• Halo effect
  What areas do you know/expect this feature to affect? Do you have any worries about possible breaking points? Write them down here.
• Performance Impact
  Could this PR affect performance? If so, what has been done to measure time taken per frame, memory used, etc.?
• Package requirements
  What Unity Editor version is required/supported? Any other dependancy packages needed?

Checklist for PR maker

• Have you added a backport label? (if needed)
• Have you updated the Changelog? Each package has a CHANGELOG.md file
• Have you added or updated the Documentation to your PR? When you add a new feature, change a property name, or change the behaviour of a feature, it's best practice to include related documentation changes in the same PR

---

Testing status

• Existing or new automation tests - what automation was added, changed
  Put any relevant Yamato links here
• Detailed description of what testing was done, what projects were run
  Tell the reviewers what did you already test, so that they may have a better understanding when reviewing/testing this PR themselves
• What environment did you test on?
  Your Operating System, Platforms you ran on, Graphics APIs and any other relevant info you can think of
• Projects
  Any existing projects ready for testing should be noted here
• Testing checklist

• Built and run editor Locally or Katana
• Built a player Android/iOS (if applicable)
• Run on device Android/iOS (if applicable)
• If new feature has UI, does it match Unity style? (Unity HIG?)
• Tested Undo/Redo + Prefab overrides + Alignment in Preset
• All items have tooltips?

---

Note to guardian

Changeset to use, if extra changesets on top. Any other notes to pass along

Comments to reviewers

Notes for the reviewers you have assigned