This test was disabled due to frequent ongoing changes to the bitstream.
Re-enabling the same, now that we are close to a bitstream freeze.

Going forward:
- Any normative changes to the bitstream will have to update the
expected_md5 value.
- On the other hand, this test allow catching any unintentional
bitstream changes.

Change-Id: I20d5252800aef4703cd5d6f408f196896e150f1d