Stop displaying module version in diagnostic

[hasithaa]

This is noticed when testing the SwanLake Alpha2 pack.

Eg:

ERROR [tmp.bal:(4:16,4:31)] incompatible types: expected 'string', found '(ballerina/file:0.7.0-alpha3:InvalidOperationError|ballerina/file:0.7.0-alpha3:PermissionError|ballerina/file:0.7.0-alpha3:FileSystemError|ballerina/file:0.7.0-alpha3:FileNotFoundError|ballerina/file:0.7.0-alpha3:NotLinkError|ballerina/file:0.7.0-alpha3:IOError|ballerina/file:0.7.0-alpha3:SecurityError|ballerina/file:0.7.0-alpha3:InvalidPathError|ballerina/file:0.7.0-alpha3:InvalidPatternError|ballerina/file:0.7.0-alpha3:RelativePathError|ballerina/file:0.7.0-alpha3:UNCPathError|ballerina/file:0.7.0-alpha3:GenericError)?'
error: compilation contains errors

Since we are not supporting multiple versions of the same module, we can simply omit the version part from the diagnostics. This will improve the readability.

@sameerajayasoma @hevayo @pubudu91 @dulajdilshan @nadeeshaan @rasika Thoughts?

[hasithaa]

We decided to remove the version part of the diagnostic.

[rasika]

+1 to remove versions from diagnostics. Still we'll be getting below due to #11056

ballerina/file:InvalidOperationError|ballerina/file:PermissionError|ballerina/file:FileSystemError|ballerina/file:FileNotFoundError|ballerina/file:NotLinkError|ballerina/file:IOError|ballerina/file:SecurityError|ballerina/file:InvalidPathError|ballerina/file:InvalidPatternError|ballerina/file:RelativePathError|ballerina/file:UNCPathError|ballerina/file:GenericError

where it should be actually file:Error

[nadeeshaan]

I would say we remove the orgname part as well. In a related note, what will happen if we have an alias?

[hasithaa]

We can have the same module name in two different organizations, hence we can't remove it.

[nadeeshaan]

We are experiencing the same issue when representing the information in VSCode as well. Please refer the bellow,