Reason good first issues

This issue proposes refactoring the `FileDescriptor` representation in the WASI standard library. Currently, it's an enum, but the author suggests converting it to an abstract type for better semantic representation, likely a remnant of older design choices.

This issue is an umbrella task to address 185 missing standard CSS properties in the coverage report. Contributors should tackle these by spec module rather than individual properties, ensuring shared value types are handled efficiently. Each addition requires updating runtime witnesses, tests, and regenerating the coverage report.

This issue proposes the removal of two unused operations, `MArityOp` and `MTagOp`, from the mashtree compiler. The rationale is that these operations are no longer utilized, indicating a cleanup task to streamline the compiler's codebase.

This issue proposes refactoring existing tests in `string.test.gr` that deal with byte manipulation. Currently, these tests use a helper function to convert byte arrays to byte objects, but with the introduction of byte literals, the tests can be simplified by directly using these literals.

This issue proposes implementing equality (`==`) and inequality (`!=`) operators for `Float32` and `Float64` types within the standard library. This is part of an ongoing effort to introduce specialized, faster comparison operations for numeric types.

The task involves fixing a memory management bug in Revery's Skia bindings. The bug causes crashes due to premature deallocation of Skia objects because OCaml's garbage collector doesn't interact correctly with Skia's reference counting. The solution requires implementing a custom OCaml smart pointer wrapper to explicitly manage reference counts, ensuring that Skia objects are only freed when no longer referenced by OCaml code.

Implement a code action in the Grain Language Server Protocol (LSP) to automatically generate a Graindoc header (similar to JSDoc) for functions when the user hovers over them. This involves modifying the source tree to expose binds and their export status, and deciding which attributes (parameters, return values, examples, since) to include in the generated header.