[question] mip: native mpy modules distribution

While compiling my C library for micropython as a native mpy module, I wondered about distribution.

There are currently several proposed methods:

1. mip packages installer - should works with mpremote mip alogside with on-board mip. (preffered for me)
2. writing a oneline command for the REPL using requests.
3. distributing the files as is (via github releases or another delivery method), where the user has to download and install them manually.

If 2 and 3 don't cause me any issues, except for the inconvenience, then I consider the mip option to be the priority because it is a documented way of delivering packages (with mpremote included). But I haven't found a recommended way to do this for packages containing native mpy for different platforms.

Since mip cannot automatically determine the target platform, it is necessary to get out of the situation using non-trivial methods such as distributing package.json separately for each platform using links/indexes/tags/branches/subdirectories whatewer, and the user must specify the platform during download.

Start by reviewing how mip packages are installed through mpremote mip and on-device mip, then examine the package.json and platform-specific links, indexes, tags, branches, or subdirectories mentioned in the issue. Compare these distribution approaches for native mpy modules targeting different platforms; done means documenting or defining a recommended way to distribute them.