It depends purely on the application you're writing. Many applications prefer availability over consistency, but the application is built to cope with inconsistent data.

Properties are only sacrificed during partitions. Due to Murphy's Law, if you assume partitions never happen they will happen more often but if you can tolerate partitions they happen really rarely.

The only way to sacrifice P is to have have a single node (i.e. non-replicated) system. So in practice it's a choice between C and P.

Not really. Both are all over because they address vastly different (literally incompatible) needs.

There is a fair bit of industry hype in the past decade or so around eventually consistent systems, because a lot of components of a business can use them, and that opens up a lot of extremely desirable performance options that can be fine tuned to the moon. But they're a real nightmare to use (i.e. often literally impossible) for anything that needs to be correct, so they are often just used in addition to the more classical consistency-oriented databases like postgres.