Update Plugin Best Practices section on Avoid Naming Collisions to include namespaces as an option

[jonathanbossenger]

Issue Description

The Avoid Naming Collisions section of the Best Practices page in the Plugin developer handbook includes the options to use prefixes, and classes, but not namespaces, to avoid naming collisions.

We do have a section on using namespaces in our coding standards, so it makes sense to add this to our plugin developer handbook as well.

URL of the Page with the Issue

https://developer.wordpress.org/plugins/plugin-basics/best-practices/

Section of Page with the issue

The section Avoid Naming Collisions

Why is this a problem?

It doesn't include namespaces as a solution

Suggested Fix

Add a section on the use of namespaces as an option, after the prefix section. Include details on how to create good namespaces based on the WordPress coding standards

[jonathanbossenger]

I originally created this issue in the Documentation-Issue-Tracker, but recently discovered the plugin handbook is now managed in this repository, so moving this issue here.

I'm also offering to create this section based on the same content in the lesson on naming collisions created for Learn.WordPress.org.

My next step will be to open a PR for review.

[davidperezgar]

Indeed, Namespaces are not considered now is a modern way to avoid name collisions. 100% agree for that. I'll be happy to review the PR.

[jonathanbossenger]

Thank you for confirming @davidperezgar

I am working on other tasks at the moment, and then I'm away for a week, and then it's Christmas/New Year, but I'll do my best to get a PR ready for review before the end of the year.