docs: fix invalid context imports in doc-examples

[danielbate]

Closes #1355

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	86.55%	6031/6968
🟡	Branches	70.05%	933/1332
🟡	Functions	77.44%	992/1281
🟢	Lines	86.55%	5778/6676

Test suite run success

1464 tests passing in 258 suites.

Report generated by 🧪jest coverage report action from e5cfcad

[arboleya]

Thanks for fixing this.

Just copying my two questions from:

• Dysfunctional code on Provider's docs #1355

1. Don't these #context bits defeat the purpose of having unit-tested docs?
2. Shouldn't these doc-examples.test.ts be placed in the doc-snippets?

In short, I think all code-snippets should be placed inside the docs-snippets package to avoid confusion.

Also, it would be good to have a way to bulletproof the use of #context to avoid breaking the snippets — is that possible? (cc @Torres-ssf)

[Torres-ssf]

Thanks for fixing this.

Just copying my two questions from:

• Dysfunctional code on Provider's docs #1355

1. Don't these #context bits defeat the purpose of having unit-tested docs?
2. Shouldn't these doc-examples.test.ts be placed in the doc-snippets?

In short, I think all code-snippets should be placed inside the docs-snippets package to avoid confusion.

Also, it would be good to have a way to bulletproof the use of #context to avoid breaking the snippets — is that possible? (cc @Torres-ssf)

@arboleya Since these #context are comments inside our code, it is hard to bulletproof them. Unless we find another approach to using them

[danielbate]

1. Agreed, we probably need to change approach completely to how these are implemented. Not 100% sure what the solution looks right now, I did some digging in the past but did not find something that was both unit testable and documentable. I'll investigate again at some point but lower priority than some of my other work. @FuelLabs/devrel may have some ideas?
2. Agreed, have raised Migrate snippets from fuel-gauge #1505