feat!: remove legacy encoding

[hal3e]

closes: #1318

This PR removes all code related to the legacy encoding.

Blocked by configurables not supporting new encoding. Issue to track: FuelLabs/sway#5727

BREAKING CHANGE:

• Rename resolve_fn_selector to encode_fn_selector

Checklist

• I have linked to any relevant issues.
• I have updated the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary labels.
• 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.

[segfault-magnet]

So configurables are broken until the sway issue is fixed? Do we plan on releasing this before the fix for whatever cyclic-dep reason?

[hal3e]

So configurables are broken until the sway issue is fixed? Do we plan on releasing this before the fix for whatever cyclic-dep reason?

IMO we should wait until we have support for configurables with the new encoding.

[digorithm]

So configurables are broken until the sway issue is fixed? Do we plan on releasing this before the fix for whatever cyclic-dep reason?

IMO we should wait until we have support for configurables with the new encoding.

Can we not wait for it, instead? The support for the new encoding in configurables might take a few days or a week, and it might delay the testnet release. Can we push this without supporting configurables (i.e., configurables would still use only the legacy encoding) for now, and add it later?

[segfault-magnet]

Let's get this merged, it's blocking the core update.

[hal3e]

So configurables are broken until the sway issue is fixed? Do we plan on releasing this before the fix for whatever cyclic-dep reason?

IMO we should wait until we have support for configurables with the new encoding.

Can we not wait for it, instead? The support for the new encoding in configurables might take a few days or a week, and it might delay the testnet release. Can we push this without supporting configurables (i.e., configurables would still use only the legacy encoding) for now, and add it later?

yes we can do that but not in this PR as here the legacy encoding is completely gone. Here is the new PR: #1357