Statistics histogram AVG_RANGE_ROWS discrepancy
As described in answer to Badly-formed histogram causes bad estimates on Nested Loop there has been a change to the way sampled statistics are calculated and stored, more particularly when scaling is applied.
As a side-effect, the value for DISTINCT_RANGE_ROWS in your case is a fraction between 0 and 1 (980.235 / 386212.6 = 0.002538071). The column has an exposed type of bigint, so it is rounded down to zero.
Clearly there can't really be zero distinct values when the range contains a non-zero numbers of rows.
One can only hope these discrepancies are cleared up at some stage; though it's hard to imagine exactly what that might look like without a potentially breaking change of data type, extending also to sys.dm_db_stats_histogram (available on SQL Server 2016 and later).
As for what you do about it, if you are convinced this is not just a display issue and is actually causing poor estimations, you should report it as a regression.