[CP] Fix analysis_options.yaml "include:" for nested folders in workspace.

[keertip]

Commit(s) to merge

https://dart-review.googlesource.com/c/sdk/+/376500

Target

stable

Prepared changelist for beta/stable

https://dart-review.googlesource.com/c/sdk/+/380205

Issue Description

When folders/package are nested in a workspace, and the analysis_options.yaml has an include: that depends on the other package, the include: does not get resolved. This fix allows for nested folders to be separate workspaces with packages. This fixes an issue that was introduced with the changes for monorepo support.

What is the fix

The analyzer maintains a map of all known workspaces and their roots, and this is built by traversing the directory structure. The fix ensures that all nested roots were added to the map before any lookup is done.

Why cherry-pick

Since the include: in the analysis options cannot be resolved, the analysis performed can report errors/warnings that should be reported, and vice versa. This leads to a poor UX and makes it difficult to code, as now the user cannot rely on the analysis results.

Risk

Low risk.

Issue link(s)

#56047

Extra Info

No response

[dart-github-bot]

Summary: The include: directive in analysis_options.yaml fails to resolve nested packages within a workspace, leading to incorrect analysis results. This fix ensures that all nested workspaces are properly registered, enabling accurate analysis of nested packages.