Add bldd case to Op::parse_opcode()

[ironcev]

Description

The bldd opcode was not covered in the Op::parse_opcode() which resulted in Unknown opcode: "bldd" error.

The remaining part of the bldd opcode integration chain is already implemented in #6254.

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[codspeed-hq]

CodSpeed Performance Report

Merging #6957 will not alter performance

_{Comparing ironcev/bldd (aab36ca) with master (f871a48)}

Summary

✅ 22 untouched benchmarks

[zees-dev]

LGTM 👍

However you please add a simple test case to validate compilation of sway code which uses this assembly instruction.
E.g. maybe something like this (introduced in recent PR for another op-code).

[zees-dev]

Not sure why the ecal tests need to be updated; I'm assuming I probably did them incorrectly on the first pass; thanks for fixing.

LGTM 👍

[ironcev]

Not sure why the ecal tests need to be updated;

@zees-dev No worries 😄 And thanks for asking for tests to be written! To your question, we have guidelines for writing E2E tests but no lints that would warn developers when not following them. Essentially, if a test could be a library and can avoid core dependency it executes faster as when core needs to be compiled. This is important, considering the amount of tests we have. And also in this case, the test's category was unit_tests_pass although there were no unit tests in it. We should have lints for such cases, it is easy to overlook it when writing test.