Keep pyproject.toml project table

[gforcada]

This is split from #355 as that is getting broader and broader 😅

Or rather, smaller PRs are simpler to review and merge ✨

Here, we ensure that if there is some special comments on pyproject.toml whatever is between them it is kept verbatim whenever config-package is run.

This is a stepping stone for #355

[mauritsvanrees]

LGTM. I tried with a simple text like this and it remained:

# START-MARKER-MANUAL-CONFIG
[random]
stuff = "test"
# END-MARKER-MANUAL-CONFIG

It breaks when the file does not exist yet though. See inline suggestion.

[davisagli]

Wouldn't it be possible to make it keep the project table without special markers?

[gforcada]

@davisagli I guess so, yes, we can read the file with tomlkit store the table and apply it after the changes.

OTOH, all other files managed by plone.meta (and also pyproject.toml) have a comment at the very top stating "DO NOT TOUCH, MANAGED BY PLONE.META".

By keeping these comments we ensure that anyone wanting to modify the trove classifiers of a random python distribution might first think "oops I can not do it (reading the comment at the top)" but then by seen the markers will think "oh, but here I can edit freely, cool".

From a developers experience I would say that keeping the markers makes more sense.

Either that, or we modify the comment at the top stating that the project table is copied verbatim whenver plone.meta is run 🤷🏾

[davisagli]

@gforcada I don't feel strongly. Try something (this way is fine) and we can adjust if needed.