Update some documentation

[richardkiss]

I found the documentation didn't quite match what I needed to do to get this to work.

[dholth]

Thanks!

[richardkiss]

@dholth I'm looking at this again now, and I'm thinking that this is probably a bug in code somewhere rather than a bug in documentation. But looking at the enscons code briefly, I can't figure out where these keys are being read.

[dholth]

https://github.com/dholth/enscons/blob/main/enscons/__init__.py#L486
https://github.com/dholth/enscons/blob/main/enscons/api.py#L49-L51
oops, that's for editable installs...

Here it is https://github.com/dholth/enscons/blob/main/enscons/__init__.py#L162-L183

It looks like the user's SConstruct is meant to parse pyproject.toml, and pass the entire project dict to enscons as metadata. Then project['scripts'] gets parsed out to create entry_points.txt. If you put all the metadata in [tool.enscons] including name, description, version then SConstruct could also pass that to enscons since the user SConstruct, not enscons itself parses toml.