[2201.9.0] Suppress the warnings from imports

[Thevakumar-Luheerathan]

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #32985

Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

• [ ] Read the Contributing Guide
• [ ] Updated Change Log
• [ ] Checked Tooling Support (#)
• [ ] Added necessary tests
  • [ ] Unit Tests
  • [ ] Spec Conformance Tests
  • [ ] Integration Tests
  • [ ] Ballerina By Example Tests
• [ ] Increased Test Coverage
• [ ] Added necessary documentation
  • [ ] API documentation
  • [ ] Module documentation in Module.md files
  • [ ] Ballerina By Examples

[sameerajayasoma]

The compiler option --showAllWarnings is too generic. We need an option that shows only the dependent package warnings, right?

We already show current package warnings. So --showAllWarnings doesn't make sense.

[azinneera]

The compiler option --showAllWarnings is too generic. We need an option that shows only the dependent package warnings, right?

We already show current package warnings. So --showAllWarnings doesn't make sense.

Considering the above comment and @nipunayf's suggestion to hide INFO and HINT diagnostics also by default, how about --show-dependency-diagnostics?

[Thevakumar-Luheerathan]

We need an option that shows only the dependent package warnings

It means, that when the user gives bal build --<option-we-introduce>, should we print only the diagnostics from the dependency package? shouldn't we print the current package diagnostics?

I thought that we don't print all these dependency package diagnostics. with the flag, we print all the diagnostics both from the current package and the dependency packages.