Ability for defining NodeCategoryAttribute for ZeroTouch methods and overriding last category part

[luxliber]

Purpose

In additiion of issue #5947

In some situations we need to make ZeroTouch nodes for addding additional funcionality for existing objects and categories.

For example:

Standard Revit Dynamo library has "Revit.View" category with nodes for working with views (Revit.Elements.View class).
And want to make ZeroTouch library with some additional nodes for working with views (for example - View.ViewName query node)

I can not make ViewName property becouse my class is not Revit.Elements.View.
I can make static method public static string ViewName(Revit.Elements.View v) but it will be assigned with "Actions" category, not "Query"

So I would like to propose ability for overriding automatic categories last part assignment for ZeroTouch methods by standard NodeCategoryAttribute. This will get developers great flexibility for organasing nodes and making clear node structure for end-users.

One difference with using attribute for ZeroTouch methods is assigning only last category part (not full path). I mean "Query" - not "MyLib.View.Query"

Impact assessment

• All tests pass using the self-service CI.

Testing strategy

Create ZeroTouch lib.
Create class and static method with NodeCategory("Query")

public class View 
{
    [NodeCategory("Query")]
    public static string ViewName(string inStr)
    {
        return inStr;
    }

    internal View()
    {
    }
}

After compiling and loading dll in Dynamo you will see ViewName node in "Query" category:

Review staging

• Architectural Design Review

Reviewers

@lukechurch

[lukechurch]

It's convention in C# to put a space between the if and the (

[lukechurch]

@luxliber Thanks very much for this!

If you could address the minor nits above, I think we'll be happy to merge this.

Thanks!

[luxliber]

@lukechurch Thanks a lot!
I`ve made changes regarding your comments and added additional "null" verifying for getting function type process