Why would optimizer choose Hash partitioning type over Demand in this plan

I created a static view with values clause and ordered the data in descending rowcount order. Most of the time I get demand partitioning and it works wonders for us, but in this plan we get hash partitioning, why would that be?
Thank you in advance.

Estimated query plan