If you want to be a software engineer instead of a "code monkey", this is part of it. The software engineer has to be able to see the second order effects of changes to the code.
In my opinion it's almost a given that any senior dev considers these. You can't be a senior dev / team lead / architect without thinking about how the system will be affected by decisions in the long run. From "MongoDB is faster, but it won't integrate with BI as well down the line" to "Well, GCP is great, but Google has a history of not supporting services in the long run."
Of course MongoDB does integrate with BI these days via its BI connector :-)
Haha, well, I won't start an argument given your affiliation, but let's just say that most BI tools CLAIMED to be able to integrate with Mongo well, but in the end, we ended up dumping the data into SQL for the BI tools. This was 4 years ago, and we tested about 5 major BI providers and were willing to pay them ridiculous sums.
With that said, I enjoy Mongo, for its specific use cases.
We built our BI connector a few years ago for all the reasons you outline. Definitely worth a spin if you have this challenge again. Basically makes MongoDB look like MySQL (if that floats your boat :-)).