Move Facility related entity checks from FacilityOps into new Facility node class(es)

[swirtSJW]

Description

The new approach created by the CMS Platform Team in va_gov_content_types makes way for adding properties and methods to classes that extend the vaNode class.

This is a much better way to address some of the work that we have scattered in calls to FacilityOps. (easy to find and replace) FacilityOps should then remain the place for data like what content types are considered facilities.

Acceptance Criteria

• [ ] Calls in FacilityOps that use the node entity should be moved to a node class extension
• [ ] Methods in FacilityOps that return an array or evaluate strings or ids should be assessed to see if they should be moved (likely not and should stay where they are to be the source of truth.)
• [ ] Items already in va_gov_content_types that are now a second source of truth for like this one should get it from FacilityOps.
• [ ] This class and this one should be moved into va_gov_vamc

[swirtSJW]

Please add your planning poker estimate with Zenhub @omahane

[swirtSJW]

@jilladams @xiongjaneg We don't really have an epic for "Aligning with CMS Platform Changes" but it might be a good idea.

[jilladams]

For now, I think we can use Technical Debt, and review that for urgency as new items pop up. (My takeaway from Scrum today.) Also noting that I flagged this topic with Berni, and Michelle is seeding with Erika, re: how CMS changes > Product changes comms work, when it starts with engineering, especially.