Design a user-facing textual grammar for Graphene nodes and networks

Currently the `CopyBufferEntry` is serialised using JSON when a user copies a layer:
```json
{
"nodes": {
"2": {
"alias": "custom alias",
"name": "Transform",
"inputs": [
{
"Node": {
"node_id": 3,
"output_index": 0,
"lambda": false
}
},
{
"Value": {
"tagged_value": {
"DVec2": [
5.049571603427239,
118.83782129742963
]
},
"exposed": false
}
},
```

However this should be changed to be in a format that looks something like:

```toml
[node parent(4) / transform(2)]
alias = "custom alias"
position = [1, 3]
vector_data = { node_id = 3, output_index = 0 }
translation = { value = [5.04, 118.8], exposed = false }
```

whereby each input is stored in snake case if it is overwritten.

Or possibly a format using the [ron](https://github.com/ron-rs/ron) grammar. This is the current line of thinking for the design.

Start by locating the current CopyBufferEntry serialization and tracing how copied layers are represented. Compare the proposed TOML-like grammar with the linked RON grammar, including node references, overwritten inputs, aliases, and positions. Done means the project has a decided user-facing grammar and a documented direction for implementing it.

Escrito por el modelo de indexación a partir del texto del issue.