Updater: resource compression

[hedger]

What's new

• toolbox: compress: added callback-based compression API for decompressing large streams at once
• toolbox: compress: added compression API for chunked reads of decompressed data
• toolbox: compress: refactored existing compressor to use callback-based API internally
• toolbox: tar: support for heatshrink compression
• cli: added storage extract command for extracting plain .tar and .ths archives at arbitrary paths
• updater: now using .tar.hs for resource bundle
• updater: split resource deployment stage progress into separate cleanup and unpack steps
• unit_tests: tests for all the new stuff
• scripts: added standalone script for packing/unpacking data with Flipper Heathshrink stream headers
• rpc: now uses heatshrink decompression for archives ending with .ths

Verification

• Run update, storage extract in CLI
• idk

Checklist (For Reviewer)

• [ ] PR has description of feature/bug or link to Confluence/Jira task
• [ ] Description contains actions to verify feature/bugfix
• [ ] I've built this code, uploaded it to the device and verified feature/bugfix

[github-actions[bot]]

Compiled f7 firmware for commit 70c95e5e:

• 📦 Update package
• 📥 DFU file
• ☁️ Web/App updater
• 📊 Size report

[github-actions[bot]]

PVS-Studio report for commit e8a2a4b2:

• Report

[CookiePLMonster]

Will the use case here be that the users are expected to compress files off-site and e.g. include compressed assets inside the FAP, or is this in preparation for FAPs compressing assets internally and decompressing during the first-time extraction step?

[hedger]

Will the use case here be that the users are expected to compress files off-site and e.g. include compressed assets inside the FAP, or is this in preparation for FAPs compressing assets internally and decompressing during the first-time extraction step?

Primary objective for this PR is to reduce resource bundle size in update package, improving update speeds.

However, with improved compression APIs, it may be reused in other subsystems.

[CookiePLMonster]

However, with improved compression APIs, it may be reused in other subsystems.

Yeah - considering that FAP asset unpacking is IO bound (as far as I can tell), and those assets can never be referenced directly without unpacking, feels like storing them compressed is a win - less IO reads, and faster FAP installation times.