[Bug]: Annotation values with mapping values panic at runtime for const annotations about ballerina-lang HOT 2 OPEN

When creating the annotation value, we make it immutable by invoking cloneReadonly. The problem occurs when populating the initial values of the record.
In the above example,

public type AnnotationRecord record {|
    string summary?;
    Examples examples?;
|};

When creating the AnnotationRecord value, we use the type of the field as Examples, and do a istypecheck with the type of the field. That is immutable.

We can fix this by making the field read-only as well.

public type AnnotationRecord record {|
    string summary?;
    Examples & readonly examples?;
|};

public type Examples record {|
    map<ExampleItem> response;
|};

public type ExampleItem record {
    map<string> headers?;
};

const annotation AnnotationRecord annot on type;

@annot {
    examples: {
        response: {}
    }
}
type Employee record {|
    int id;
    string name;
|};

The problem occurs, we call cloneReadonly on {examples: {response: {}}} and set the type correctly. However, the type of {response: {}} is set to Examples, and we do not create cloneReadonly for this.

from ballerina-lang.

As a workaround for this issue, we can define the Examples type as read-only.

from ballerina-lang.