Companies just plan for redundancy in roles so they are ready when people need to take parental leave or sabbaticals. It isn't that difficult for a company to handle, but companies in countries where this isn't the norm just plan and hire for it.
Right, the main difference there would be that the changes get combined into one squash commit rather than a merge commit. Mostly an aesthetic choice, so I could definitely see both as viable.
If I wanted to move changes between branches I would probably prefer a squash rather than a regular merge, as that will look cleaner in the history.
This sounds like a Product Owner to me. Indeed, all these types of roles are pretty much interchangeable depending on the exact structure of your teams.
I would even say: in every case, except where a GPU or TPU is necessary to achieve a certain speed. Unless there are very specific reasons for it, GPU/TPU is just unnecessarily cost inefficient.
I wouldn't count on it. As long as the product is available and marketed in other countries they can get caught in legal issues for not following those countries laws relating to marketing and offering of products.
I'm not sure about this, but it seems that the Japanese Dean and DeLuca is just a Japanese company owning and operating the brand under license or joint venture. This is how a lot of foreign brands enter Japan (for example, Taco Bell and Baskin Robbins), and why many remain even when the original company more or less goes under (for example, Mister Donut). I wouldn't be surprised if this ends up being the same.