chore: update community files and workflows for org migration

[TasoOneAsia]

Proposed changes

Closes #386

Checklist

Before creating a pull request (PR), run through this checklist and mark each as complete:

• I have read the contributing guidelines.
• I have signed the F5 Contributor License Agreement (CLA).
• The PR title follows the Conventional Commits specification.
• If applicable, I have added tests that prove my fix is effective or that my feature works.
• If applicable, I have checked that any relevant tests pass after adding my changes.
• I have updated any relevant documentation (e.g. README.md).

[alessfg]

I made a few suggestions, mostly style related. Generally speaking, looks like we have slightly different default editor options which leads to some incongruences between our setups:

1. There are no blank lines at the end of files
2. Markdown gets automatically split amongst multiple lines
   It would be great to get those adjusted to the standard format across the other community OSS repos.

In so far as other changes:

1. For consistency purposes, can we also rename f5-cla.yml to f5_cla.yml and ossf-scorecard.yml to ossf_scorecard.yml?
2. Can you add a badge linking to the community forum and the license to the README (https://github.com/nginx/template-repository/blob/main/README.md?plain=1#L4-L5)? The copyright needs updating too 😄
3. The PR template CLA link also needs to be updated

[alessfg]

Found some more minor style changes that would be nice to have 🙃