Report creation script

[PaulFarault]

Provide a script to easily create new meeting notes reports.

Usage

npm run reportinit

Result

Create a yymmdd-contributors.md file on a new yymmdd-contributors-report branch containing a template populated with the pending PRs. For example:

---
type: contributors
date: 2023-10-28
description: |
<main topics of the meeting>
---

# TDP contributors meeting notes

<!-- general notes -->

## Pull Requests

Weekly review of open PRs (in chronological order):

- [tdp-ui#198](https://github.com/TOSIT-IO/tdp-ui/pull/198): <!-- status of "Release automation" -->
- [tdp-collection#745](https://github.com/TOSIT-IO/tdp-collection/pull/745): <!-- status of "WIP: 612 yarn timeline v2" -->
- [tdp-ui#210](https://github.com/TOSIT-IO/tdp-ui/pull/210): <!-- status of "chore: add dev environment without auth" -->

## Open topics

<!-- open topics -->

[wdavidw]

1. Scripts are located inside bin
2. the entry point shall be the foundation of a future scalable API without backward incompatibilities, the entry point shall be generatic, eg npx tdp <command> <args> (use Shell.js)
3. the command, initReport shall accept additional commands as part of a more complex API, report init and not init report

[PaulFarault]

1. Scripts are located inside bin

All other TOSIT-IO project use a scripts directory. I think it's best to do the same here.

2. the entry point shall be the foundation of a future scalable API without backward incompatibilities, the entry point shall be generatic, eg npx tdp (use Shell.js)
3. the command, initReport shall accept additional commands as part of a more complex API, report init and not init report

This is a simple script that I share for convenience. If we want to build a whole CLI I suggest we do it in a next iteration.

I renamed the script to reportinit.

[PACordonnier]

Thanks @PaulFarault, I'm not able to review code but feature is very useful !