Obviously, there are 2 main aspects to this:
1. The period of time that 3CX will support the phone via provisioning, and
2. The period of time that the phone manufacturer will support before declaring EOL (end of life) and EOS (end of support).
Keep in mind that 3CX is using SIP and as it is an non-proprietary protocol, this in and of itself provides some assurance of the devices' usefulness beyond what other proprietary systems may offer. I know of no manufacturer who has a defined product life cycle that is made known beforehand. They usually have a roadmap and live with the product as long as there are adequate sales and there is nothing in the cycle (technology/hardware/software) that precludes the device from being competitive within its market-space or incapable of being advanced/updated. Once sales or margins decline (for whatever reason) they will usually start the EOL cycle which will include the Date for last sales, date of last support and then End of Life date, By this time, they usually already have a successor in the pipeline.
I have clients using both older Yealink, Grandstream and Aastra phones (10 years old now) that continue to serve their purpose and all are long past EOL from the maker.
While 3CX may elect to no longer support a phone, this, to me, merely means that they have moved on to more current makes/models and will no longer provide templates by which to ease the provisioning aspect. However, the phones will continue to work as long as the SIP protocol version in use at the time is used by both the PBX and phone(s).
One thing, is that while the phone may have an EOL, at least I likely won't have to replace the PBX as well as I might with proprietary brands.