Re-word "CF 1.5/1.7" label and use to collate netcdf/CF issues

[pp-mo]

I'm hopeful that, shortly after Iris 3.0, we can plan to do some rework on netcdf loading and CF support.

Only some of that work is about supporting new CF features, some of it being more of internal code work,
especially what would be involved in retiring/replacing Pyke (#3415).

So I suggest renaming the "Feature : CF 1.6/1.7" to "Feature : netcdf+CF"
And I would add to that label, at least the following related issues :

• Replace pyke package with other solutions for netcdf loading #3415
• Promotion of dimension coordinates when loading #3343
• Netcdf load should workaround unexpected names in 'coordinates' #3644
• Make CoordSystem Implementation Consistent #3409
• Clarify behaviour of "wrapper" objects derived from CFVariable. #3725
• NetCDF global attributes vs data variable local attributes #3325

[pp-mo]

@bjlittle do you approve this approach ?
It seems to me that our other existing "Feature" labels are ongoing categories rather than specific goals+targets, so I think this re-purposing of the CF label would make sense..

[bjlittle]

We've not openly discussed it, but yeah it seems that through use the Feature labels tend to be for on-going themed work.

It makes sense to me to re-badge that lable to be more openended and inclusive, rather that CF version specific.

I've no objections... so go for it 🚀

@SciTools/iris-devs Any other opinions?

[pp-mo]

Ok, I'm just doing this...