[dv,cov,mubi] The cp_value coverpoint in dv_base_mubi_cov doesn't handle Width=32 properly

Description

If you look at an overnight test for rv_dm, you'll see a very low functional coverage number. This turns out to be due to mubi coverage of the late_debug_enable register (a 32 bit mubi register). The coverpoint in question is in dv_base_mubi_cov.sv and is

    cp_value: coverpoint value {
      bins true = {ValueTrue};
      bins false = {ValueFalse};
      bins others[Width] = {[0:{Width{1'b1}}]} with (!(item inside {ValueTrue, ValueFalse}));
    }

Unfortunately, this doesn't pick up Width correctly. You would expect this to have Width+2 = 34 bins but last night's coverage shows it having 409 bins(!). Assuming that the +2 is working correctly, I'm not sure how the others bins array could have had 407 elements.

Debugging locally, I hacked the file to say others[32] = .... I ended up with 34 bins as you'd expect

The result of this issue is a low fcov score for the block for a slightly silly reason.

Start in dv_base_mubi_cov.sv at the cp_value coverpoint and inspect how Width is interpreted in the others bin range and array size. Reproduce the behavior for the 32-bit late_debug_enable register in the rv_dm overnight coverage result. Done means the coverpoint reports Width+2 bins, rather than 409, and the resulting coverage is correctly represented.