Feature/#507 separate package long desc with readme

[trgiangdo]

Resolves #507

In this PR:

• Add a "package_desc.md" file for each taipy package and use that instead of "README.md" on "setup.py"
• Remove redundant "CONTRIBUTING.md" files in subpackages
• Minor updates on "README.md" files and "INSTALLATION.md" files

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
18436	16129	87%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
taipy/config/setup.py	0%	🟢
taipy/core/setup.py	0%	🟢
taipy/gui/setup.py	0%	🟢
taipy/rest/setup.py	0%	🟢
TOTAL	0%	🟢

updated for commit: 404685d by action🐍

[jrobinAV]

I would take the opportunity to:

• Remove all sub-package CODE_OF_CONDUCT.md
• Merge all sub-package INSTALLATION.md into README.md
• Remove for all sub-packages, the 3 sections (running the tests, contributing, and code of conduct) of the package_desc.md

[trgiangdo]

Since each sub taipy folder is still a standalone package, I think it's a good practice to have its own "CODE_OF_CONDUCT.md", even if it's duplicated, we never change it anyway.

For the "INSTALLATION.md", I think we can keep it but no strong opinion. Keep in mind that the content of the installation instruction can be added to the "package_desc.md" as a link to the "INSTALLATION.md" file, it must be a Github link, which is possible.

I would keep the contributing and code of conduct sections in Pypi description since it's quite useful information and link directly to our doc anyway

[florian-vuillemot]

I agree; I think Pypi users want a description, information on license, security and maintenance, and a link to the documentation. Since you can't contribute on Taipy, a contribution section doesn't make much sense.

[florian-vuillemot]

Having just one "CODE_OF_CONDUCT.md" is enough, IMHO, because, as you said, it's the same everywhere, and it is not helpful information on Pypi.
I completely agree with you about the contribution file. Having a "CONTRIBUTING.md" in each folder makes a lot of sense, with the CONTRIBUTING.md at the root of the repository acting as a proxy for the others. Nevertheless, I wouldn't put this file on Pypi because it doesn't bring any value to the user using the package.