Ballerina good first issues

The `data.yaml` module incorrectly serializes multi-line strings by replacing newline characters with the literal 'n' instead of the intended backslash-n escape sequence. This is due to an incorrect use of `String.replaceAll` which treats the replacement as a regular expression. The fix involves using `Matcher.quoteReplacement` or `String.replace` to ensure proper escaping.

This issue proposes refactoring the HATEOAS support in the Ballerina to OpenAPI tool. The goal is to leverage the parsed `ExpressionNode` directly from the syntax tree instead of manually parsing string values for annotation fields. This change aims to simplify the code and eliminate redundant parsing logic.

This issue proposes an enhancement to the WebSub module, allowing subscribers to register for multiple topics within a single subscription request. This would streamline the subscription process and improve efficiency for users managing multiple subscriptions.

This issue highlights that the `toAvro` function in the Ballerina Avro library silently alters values that don't conform to the schema, instead of throwing an error. Three specific cases are detailed: out-of-range integers wrapping, floats truncating into integers/longs, and any type being stringified. The core question is whether these silent alterations are intended behavior or bugs.

The `data.yaml` module currently panics when encountering a nested mapping under an assigned key in a YAML string, instead of returning a `yaml:Error`. This is because an unchecked `RuntimeException` is thrown, which is not caught by the parser. The fix involves throwing a specific `YamlParserException` to allow for graceful error handling by callers.

The HTTP compiler plugin fails to report ambiguity diagnostics for resources within HTTP service classes and service objects, unlike equivalent resources in service declarations. This means that potential ambiguities in how payloads are handled in these service forms are not being flagged, leading to inconsistent error reporting. The issue requires extending the analyzer validation to cover service classes and service objects.

The `data.yaml` module incorrectly uses `Matcher.find()` instead of `Matcher.matches()` for scalar tag resolution, leading to `NumberFormatException` for invalid integer formats like '12abc' and '0xZZ'. The fix involves replacing `find()` with `matches()` and adding guards to the octal/hex parsing to ensure `YamlParserException` is thrown as expected.

A bug in Ballerina's HTTP module causes header parameters with default values to be treated as mandatory, resulting in a 400 Bad Request error when the header is omitted. This behavior is inconsistent with query parameters, which correctly utilize their default values when not provided. The issue affects Ballerina Swan Lake Update 8.

The provided Ballerina program crashes with a NullPointerException when attempting to print a `sql:ParameterizedQuery` within multiple concurrent `printer` functions. The issue appears to stem from how the `io:println` function handles the `sql:ParameterizedQuery` type when called concurrently.

The user requests the ability to modify the `Settings.toml` file using the `bal` command. This would allow for easier management of different configuration profiles for various development environments, such as dev central, and also suggests moving environment variables like `BALLERINA_DEV_CENTRAL` into `Settings.toml` for convenience.

The error message for duplicate map entries in the data.yaml module incorrectly displays an unsubstituted template literal `${key.toString()}` instead of the actual duplicate key. This is due to a mismatch in interpolation syntax between Ballerina/JS and Java, and the error message also has an unbalanced quote. The fix involves correctly substituting the key and balancing the quote in the error message.

The Ballerina Avro package's `Schema` initialization panics when provided with an invalid schema string. According to the specification, it should return a proper error instead of crashing. The provided sample code demonstrates this behavior, resulting in a `SchemaParseException`.