feat: add warning for package in a workspace not listed as member

[khayss]

Description

This PR closes #4451

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.

[fuel-cla-bot]

Thanks for the contribution! Before we can merge this, we need @khayss to sign the Fuel Labs Contributor License Agreement.

[khayss]

@IGI-111
I'm making this draft PR to discuss some details about implementing this feature.

Since this is inspired by Cargo design, I have studied how Cargo achieves this feature, and I have the following questions that will be helpful in completing this feature.

1. Is there a current functionality to locate the workspace manifest from a sub-directory?
2. Is there any recommendation on where this feature should be implemented? i.e., location or module?

Anticipating your response 🫡

[khayss]

@IGI-111 any update?

[kayagokalp]

Thanks for the PR, we seem to have lots of cargo references here in the code, I haven't checked the overall code but this seems to me either fully LLM generated or copy pasted from cargo, which probably won't be working if we push it like this :) I can help out if you need pointers but this PR as it is not seem to be going in a correct direction.

First of all we need to be re-using availble stuff from forc-pkg and forc-util, in forc side you need to check if we are in a workspace, in new and init commands, if so we should add ourselves (the package we are processing) to the workspace.

If we invoked forc build, we should again check if we are in a workspace, if so we should warn and say that this appears to be in a workspace but not listed as a member, this check probably needs to happen on forc-pkg side.

To summarize we need to ensure we can do this check on forc-pkg side, and invoke this check for new, init and build. Simply consume it differently on new, init and build scenerios

[khayss]

Thanks for the update @kayagokalp
I reused some codes from Cargo and restructured where necessary. I'll have a look at the requested changes and implement them.

[khayss]

Also, for my question, I'd like to know if there's a logic to locate a workspace manifest from a sub-directory?

@kayagokalp

[khayss]

Hello @kayagokalp
Pls check and review

[khayss]

I understand where the feature is to be implemented. For now, the most important thing is having a way to find the workspace manifest from the current directory. This current draft aims to solve that, as there's no such functionality yet. If this is reviewed, and it's cool, I can proceed to finish up the feature