[Bug]: Profiler console output contains invalid characters

[HindujaB]

Description

$subject

Steps to Reproduce

Create a bal package and run bal profile.

Note the ? character in the console output.

Affected Version(s)

2201.8.2

OS, DB, other environment details and versions

Windows 10

Related area

-> Runtime

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[gabilang]

It's due to the code-page used in windows CMD is 437 by default. This code-page prevents to show the Unicode characters properly. If we change the code-page to 65001, it will show the Unicode characters properly.

We can change the code-page of the windows CMD by using the command chcp 65001.

[gabilang]

In order to keep a consistent terminal/cmd output pattern across platforms, we can use a character which is supported in the code-page 437 for bulleting or we can remove the bullets.
As per an offline discussion, we decided to not to use bullets instead use right indentation.
The output log is going to look as follows,

================================================================================
Ballerina Profiler: Profiling...
================================================================================
Note: This is an experimental feature, which supports only a limited set of functionality.
[1/6] Initializing...
[2/6] Copying executable...
[3/6] Performing analysis...
[4/6] Instrumenting functions...
      Instrumented module count: 44
      Instrumented function count: 3981
[5/6] Running executable...

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.