Add notes about naming of personal tokens to "Hack for LA's GitHub Actions" Wiki page

[t-will-gillis]

Overview

As developers testing GitHub Actions, we want to be sure that the tests we run are contained to our own repos, and do not cause unexpected changes to the Hack for LA environment. When generating personal access tokens for testing GHAs, developers need to follow best practices to mitigate these effects.

Action Items

• We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Please refer to How to Contribute to the Wiki for instructions about where to place "Content to be Added/Edited in the New website-wiki Repo."

• Refer to the Hack for LA's GitHub Actions wiki page, and specifically Tip 7: Using Personal Access Tokens to test in your own Project Board. Select 'Edit' and scroll down to "Tip 7". Under the dropdown "9. Name the secret and paste the secret token into the textbox", below the image and the closing </details>, replace:

Now, when you are testing the GitHub Action in your own Project Board, you will replace `secrets.HACKFORLA_BOT_PA_TOKEN` with `secrets.[your new token]`. Once you are satisfied with the changes in your own system, change it back to `secrets.HACKFORLA_BOT_PA_TOKEN` before making your pull request so that token for the HfLA Project Board is not pointing to a secret that doesn't exist. 

with:

In the box "Secret*", paste the token code that you saved in step 5.  

In the box "Name*", enter a name for your token, for example  `MY-TEST-TOKEN`. **Important note**: Do NOT give your token the same name that you see in the yml file- **you must change it** to avoid unexpected behavior. Now, when you are testing the GitHub Action in your own Project Board, you will replace `secrets.HACKFORLA_BOT_PA_TOKEN` with 'secrets.' + the name of your token, for example `secrets.MY-TEST-TOKEN`. Once you are satisfied with the tests in your own system, change the token name back to `secrets.HACKFORLA_BOT_PA_TOKEN` before making your pull request so that token for the HfLA Project Board is not pointing to a secret that doesn't exist. 

• Follow the instructions for including the edited content as explained in Editing a Wiki page.

Resources/Instructions

• Hack for LA's GitHub Actions wiki page

[ExperimentsInHonesty]

@t-will-gillis We are not adding new items to the wiki right now. There is some default text that should be placed on the issue. look up some of the other wiki issues to find it.