Update security policy

[k9withabone]

Added MAINTAINERS.md with contact information for the Podlet maintainers.

Changed SECURITY.md to direct security vulnerability reports to the Podlet maintainers.

Closes: #183

[k9withabone]

@Luap99 does the new security policy look good to you? I'll copy it over to compose_spec_rs (with the relevant modifications) once it is merged here.

[Luap99]

sure, LGTM. Thank you!

[TomSweeneyRedHat]

This is a bit of a circular loop and just points to this page. Maybe be a bit more explicit? If you take this suggestion, take the line above too. It's a two-for-one deal.

Suggested change

	[private security vulnerability reporting](https://github.com/containers/podlet/security) on GitHub
	"Report a vulnerability button on the [private security vulnerability reporting](https://github.com/containers/podlet/security) page on GitHub

[k9withabone]

Thanks for the review and suggestions! Does it make more sense now?

podlet/SECURITY.md

Lines 3 to 9 in 7d86818

	## Reporting a Vulnerability
	If you have identified a security vulnerability in the Podlet project, please **do not** report the
	issue publicly via GitHub issues, mailing list, Discord, etc. Instead, use GitHub's private
	security vulnerability reporting feature by pressing the "Report a vulnerability" button on the
	repository's [security](https://github.com/containers/podlet/security) page or privately contact one
	or more of the [maintainers](./MAINTAINERS.md).

podlet/MAINTAINERS.md

Lines 3 to 5 in 7d86818

	Podlet is a community project maintained by volunteers. They may be contacted directly in case of a security vulnerability.
	However, if possible, please use GitHub's private security vulnerability reporting feature by pressing the "Report a vulnerability" button on the repository's [security](https://github.com/containers/podlet/security) page.
	For all other communication, please use one of the [communication channels](./README.md#Communication).

[TomSweeneyRedHat]

See next

Suggested change

	issue publicly via GitHub issues, mailing list, Discord, etc. Instead, use the
	issue publicly via GitHub issues, mailing list, Discord, etc. Instead, press the

[TomSweeneyRedHat]

I really like where this is going, just a few suggestions to make it a bit more explicit.

[TomSweeneyRedHat]

LGTM
TYVM for the changes!