v0.152.71

• Ship mise as one of chase's apps, configured as every other is: chase.apps.mise says the package and the configuration bound read-only, a tier turns it on with enable, and its installs and downloads are kept at a scope that follows the tier's caches unless it says otherwise -- session overlaying the host's, tier a store of the tier's own with its shims on PATH, host the host's, with the same mise at both paths so a shim either side writes runs on both -- while its state, what mise trust has trusted, is never kept: the host's is overlaid in every scope, and what a session trusts goes with it (f76c49b)