Change the name of the AirflowNetwork group

[jasondegraw]

Pull request overview

Since we're keeping around groups after all, this PR changes the name of the group that contained all of the AirflowNetwork objects to be somewhat more accurate. It isn't really a traditional defect, but that's the thing that is closest. I do not know if the DoNotPublish label should be applied as well.

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

• Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
• Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish

Reviewer

This will not be exhaustively relevant to every PR.

• Perform a Code Review on GitHub
• If branch is behind develop, merge develop and build locally to check for side effects of the merge
• If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• If feature, test running new feature, try creative ways to break it
• CI status: all green or justified
• Check that performance is not impacted (CI Linux results include performance check)
• Run Unit Test(s) locally
• Check any new function arguments for performance impacts
• Verify IDF naming conventions and styles, memos and notes and defaults
• If new idf included, locally check the err file and other outputs

[Myoldmopar]

Pulled develop in for clean CI results. Anyone have any possible issue with changing this group name? I don't have any issue with it.

[Myoldmopar]

Custom check results are expected until license year PR goes in. Windows didn't respond because the CI machine went down. No one else commented about the group name. This is good to go in, thanks @jasondegraw