Redesign the issue reporting system

Fiji has a Bug Submitter for the Fiji BugZilla. We want to retire this, in favor of general SciJava functionality: a new issue reporting system, which interfaces with GitHub Issues—and the potential to write additional plugins, too. It could live in scijava-common, or a scijava-issues component if there are new dependencies. And a UI would exist in scijava-ui-swing. The issue reporter would support reporting bugs against components (i.e., JAR files) which have embedded Maven POMs that specify an issueManagement section with a compatible issue tracker. And of course there would be reasonable defaults—e.g., ImageJ would be configured to use imagej/imagej by default if the user does not specify a component.

Start by reviewing the existing Fiji Bug Submitter and the proposed scijava-common, scijava-issues, and scijava-ui-swing boundaries. Define the issue-tracker/plugin and Maven POM component behavior, GitHub Issues integration, defaults, and UI before implementation; done means the replacement system supports these reporting paths.

Written by the indexing model from the issue text.