C
There are two nested questions here - availability of the Omega2 module specifically, and availability of the MT7688 SoC around which it is built.
In terms of the module, the Omega2 is just the most well known of several MT7688 solutions from several different vendors; in doing a product it makes sense to consider all of them and what the migration path from one to another would be.
Predicting the availability of the MT7688 itself is a bit more complicated, but then it is basically just an SoC intended to run Linux in a cheap wifi router, which has been marketed for additional IoT purposes, so doing a design in such a way that porting to a successor or competing SoC would not be too painful, is a means of future proofing. Software wise this is fairly simple as long as you are building your key dependencies from source; hardware wise, the more distinct interfaces you use the more complex it becomes.
