Structural Types Schema support (#517)

[987Nabil]

fixes #517
/claim #517

This PR is build up on my PR for #518 so #589 should be reviewed first.

[Copilot]

deleted

[987Nabil]

@jdegoes @plokhotnyuk Structural types are a little tricky especially in Scala 3.
So for example

type PersonLike = { def name:String; def age:Int}

val aPersoon: PersonLike = new Selectable {
...
}

Will not be recognized by the compiler as a Selectable since the type Person is not a subtype of it.
so aPerson.name is a compile error, unless you import the implicit conversion that enables reflection.

One could suggest, to create a class

final class Record(...) extends Selectable {
...
}

So that this is returned by Schema#structural

val structuralSchema: Schema[ Record {def name: String; def age: Int}] = nominal.structural

But this is fundamentally flawed, since it defeats the purpose of the structural typing.
What I mean is, that if I have a

case class Person(name: String, age: Int)

This is not of type Record {def name: String; def age: Int} so structuralSchema would not be a schema for Person.
Maybe one could offer an implicit conversion, that uses a macro to compile time check that we can create a transformation from Person to Record {def name: String; def age: Int} but idk if this is really a good idea.

Instead my current solution offers that .structural does not return Record {def name: String; def age: Int} but {def name: String; def age: Int} and uses reflections. Which in return means, this is a JVM only solution.
Schema#structural on JS/Native leads to a compile errors.
Deriving a Schema for Record {def name: String; def age: Int} though works on all platforms

//Works on JVM, JS, Native
val structural = Schema.derived[Record {def name: String; def age: Int}]

[jdegoes]

@987Nabil Please update, rebase, and refactor to handle refinement types on DynamicValue. 🙏

[jdegoes]

@987Nabil Pleaes re-open when ready. 🙏

[BenraouaneSoufiane]

@987Nabil Pleaes re-open when ready. 🙏

What to do with this, I was waiting him to fix 28 test errors, I'm going to fix them then submit my pr as they coming from this implementation not my implementation but my implementation depends on them!

[Copilot]

Pull request overview

Copilot reviewed 34 out of 34 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Duplicate line detected. Line 220 is identical to line 219, creating a duplicate entry in the tuple list. This will cause the same field name and type name to be added twice to the fieldInfos list, leading to incorrect type name normalization.

Suggested change

(name, reflect.typeName.name)