Port to clio

[wagoodman]

This PR replaces what common patterns have already been established and hoisted into clio and bubbly. See DEVELOPING.md additions made in this PR for more details on the package layout.

At a high-level, here are the changes:

• Removes the application object, eventloop, logger UI, config loading, version command, flag binding with viper, and profiling concerns (replaced by clio)
• Removes bubbletea components (replaced by bubbly)

High level focuses of this PR:

• lean into stronger separation of concerns and make it more difficult to accidentally misuse elements in the wrong package (e.g. by pushing internal packages lower in the API when possible)
• focus on CLI-lib and core-lib divisions and usage
• foster re-use of common patterns across applications when warranted

Detailed changes:

• removed CLI interaction from the core lib (load.P12 -> loadP12Interactively) as this is a CLI concern.
• splits the UI (an internal concern) and the handling of UI events into bubbletea models (a CLI lib concern). This allows for shared UI interactions for lib users of quill in the same way that grype uses syft UI elements in the grype UI. (see cmd/quill/cli/ui/handler.go and cmd/quill/internal/ui/ui.go)
• version extracted from the build derived from ldflags is a main package-only concern, thus, this information is injected downstream from main instead of pulling from a package in static-fashion (see cmd/quill/main.go). Why? because this can only be valid when the build is controlled since specific ldflags are required.
• replaced the log redactor with the common go-logger log redactor
• the event child packages have been combined into the event package. Why? This separation seemed weak, where the original reason was to separate the definitions of events from the capabilities, however, this does not apply to these monitor/parser objects.