generate policies using go generate

[iaiw3br]

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: Policies are created manually

Solution: Automatically create policies using a template and the go generate command.
To generate files need to use make generate command

Testing: Manual testing, I ran the command and got the generated files

Please focus on paths of the files or directories which I set.
I pushed this code to know can I use this method to generate policies ?

Closes #ISSUE

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

NONE

[github-actions]

🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the F5 CLA and reply on a new comment with the following text to agree:

---

I have hereby read the F5 CLA and agree to its terms

---

Artem Ivanov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[iaiw3br]

I have hereby read the F5 CLA and agree to its terms

[sjberman]

Thanks for doing this! Would you mind also including the issue number in the PR description so that it will be closed when the PR is merged?

[sjberman]

Let's deduplicate the common template and main function that we have in both v1alpha1 and v1alpha2 into a common file, maybe in apis/ top-level. Then we can just include the specific policy lists in each api version directory.

The package version at the top of the template could also be provided as a templated value.