pull,package_info,ui,cli: report the pull flow via BuildView

Retire the ProgressCallback option-of-closure, the one pre-port
reporting idiom left in the tree: pull and package_info::lookup now
take &dyn BuildView like every other core flow, and the announcements
map onto message (unsized work), progress (item counts: series probes,
git objects, extraction) and progress again for byte downloads, which
the old callback carried in the same 4-argument shape.

The terminal side swaps the (ProgressBar, closure) pair for PullView, a
BuildView implementation owning one bar of the shared MultiProgress
with the same spinner/transfer style switching; it releases the line on
drop, which the CLI triggers explicitly on both outcomes since
exit(1) skips destructors. Headless callers (tests, internal lookups)
pass &report::Quiet. git clone sideband parsing is skipped entirely
when the view is not enabled, matching the old None-callback shortcut.

src/lib.rs

@@ -63,13 +63,6 @@ pub(crate) mod test_support;
 /// Utility functions
 pub(crate) mod utils;
 
-/// Optional callback function (taking 4 arguments)
-/// - Name of the current main operation (e.g. pulling package)
-/// - Name of the current nested operation (e.g. cloning git repo)
-/// - Progress, position, index of current operation (e.g. amount of data downloaded)
-/// - Total amount for current operation (e.g. size of the file to download)
-pub type ProgressCallback<'a> = Option<&'a dyn Fn(&str, &str, usize, usize)>;
-
 /// Returns the architecture of current CPU, debian-compatible
 pub fn get_current_arch() -> String {
     match std::env::consts::ARCH {