Change Security Policy to Direct to Podlet Maintainers and Add Maintainers List

[k9withabone]

It has been requested by the Podman maintainers that Podlet have its own security policy. Currently, the security policy links to the general one for the containers org as that was what was originally requested when Podlet moved to the org.

I suggest that Podlet primarily use the security vulnerability reporting on GitHub. I have enabled private security vulnerability reporting for the repository. We could also add contact information to the requested MAINTAINERS.md file and direct security reports there. In terms of announcements, vulnerabilities can be described in the notes for the release that contain the fix.

[TheRealBecks]

1. Using the Github security vulnerability reporting system seems to be a good idea. We should also enable/add a menu when creating an issue that lets you choose a "Security issue" that links to the security vulnerability reporting system. Check Podman as an example: https://github.com/containers/podman/issues That also includes a SECURITY.md file like https://github.com/containers/podman/blob/main/SECURITY.md
2. We should add and copy CODE-OF-CONDUCT.md https://github.com/containers/podman/blob/main/CODE-OF-CONDUCT.md
3. We should add and copy MAINTAINERS.md https://github.com/containers/podman/blob/main/MAINTAINERS.md
4. A CONTRIBUTING.md already exists. Do we need to update the file?

[k9withabone]

We should also enable/add a menu when creating an issue that lets you choose a "Security issue" that links to the security vulnerability reporting system.

It looks like this is done with issue templates. Is that something you could work on when have the time?

2. We should add and copy CODE-OF-CONDUCT.md https://github.com/containers/podman/blob/main/CODE-OF-CONDUCT.md

Already done when Podlet moved to the containers org.

5. A CONTRIBUTING.md already exists. Do we need to update the file?

I don't think so, but feel free to review it.