Update code to conform to WP coding standards

[bmarshall511]

Is your enhancement related to a problem? Please describe.

Creating this to better track the progress of updating the code to better comply with WP coding standards, see #117 (comment)

• Update (6/28/23) - The remaining items left are a little more involved, see Update code to conform to WP coding standards #118 (comment)

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[bmarshall511]

👋 @jeffpaul @peterwilsoncc, I've tackled most of the coding standards issues 🛠️, but there are still a few left concerning hook names using slashes vs. underscores. I'm a bit hesitant to make these updates, as others might be utilizing those hooks in their implementations and I don't want to accidentally break anything 😅. Additionally, there's quite a bit to address regarding processing form data without nonce verification. It seems like that will require more extensive work than just updating a few lines, so it might be better to handle it through a separate issue. Let me know what you all think. 💭

[jeffpaul]

@bmarshall511 splitting out the different concerns into separate PRs should help ensure the "easy" ones get out quickly while any deeper conversations only hold up the more "complex" updates

[bmarshall511]

Sounds good @jeffpaul! I went ahead and submitted a PR for the first round of the easy ones 👆 Once reviewed & merged, do you wanna keep this open to track the harder ones or open a new issue?

[jeffpaul]

@bmarshall511 fine to keep this one open or open a subsequent one with specifics on the more complex updates, dealers choice.

[bmarshall511]

@jeffpaul Sounds good, I'll just leave this open & updated the desc. Running the linter should provide enough specifics of what's remaining.