Add mapping() and resolving() to supply custom (un)marshalling logic

[thekid]

Given the following user type:

class User {
  public function __construct(public int $id, public string $name) { }
}

Defaults

$marshalling= new Marshalling();
$value= $marshalling->marshal(new User(0, 'root'));
// ['id' => 0, 'name' => 'root']

$user= $marshalling->unmarshal($value, User::class);
// User(id: 0, name: 'root')

Custom logic

$marshalling= (new Marshalling())
  ->mapping(User::class, fn($user) => ['uid' => $user->id])
  ->resolving(User::class, fn($value) => new User($value['uid'], posix_getpwuid($value['uid'])['name'])
;
$value= $marshalling->marshal(new User(0, 'root'));
// ['uid' => 0]

$user= $marshalling->unmarshal($value, User::class);
// User(id: 0, name: 'root')

[thekid]

Released in https://github.com/xp-forge/marshalling/releases/tag/v2.3.0