Feature Request: Include main processor annotations in program details

[0xchase]

Currently Engine::getProgramDetails returns json with the following structure.

{
    "inputs": [ ... ],
    "outputs": [ ... ],
    "mainProcessor": "someProcessorName",
    "mainProcessorLocation": "SomeFile.cmajor:15:7:"
}

In particular, the createProgramDetails method inserts the name and location of the processor, but excludes any additional annotation appended to the main processor.

cmajor/modules/compiler/src/backends/cmaj_EngineBase.h

Lines 121 to 130 in 722cba9

	if (mainProcessor != nullptr)
	{
	details.setMember ("mainProcessor", mainProcessor->getFullyQualifiedReadableName());
	if (auto location = mainProcessor->context.getFullLocation().getLocationDescription(); ! location.empty())
	details.setMember ("mainProcessorLocation", location);
	}
	details.setMember ("inputs", getProgram().endpointList.inputEndpointDetails.toJSON (true));
	details.setMember ("outputs", getProgram().endpointList.outputEndpointDetails.toJSON (true));

Thus, (to my knowledge) there isn't a way to retrieve a list of user annotations added to the main processor. So if I had main processor annotations like the following, there would be no way to retrieve the width and height values.

graph ElectricPiano  [[ main, width: 300, height: 200 ]]

This feature request proposes that additional annotations added to the main processor be included in the program details. There are various ways to achieve this; one is the refactor below.

{
    "inputs": [ ... ],
    "outputs": [ ... ],
    "mainProcessor": {
        "name": "someProcessorName",
        "location": "SomeFile.cmajor:15:7:",
        /* additional annotations below */
    },
}

Another would be

{
    "inputs": [ ... ],
    "outputs": [ ... ],
    "mainProcessor": "someProcessorName",
    "mainProcessorLocation": "SomeFile.cmajor:15:7:",
    "mainProcessorAnnotations": { /* additional annotations here */ }
}

I'm assuming there isn't a way I'm unaware of to retrieve these annotations. If this is a change you're amenable to but it'd be low on your priority list, I'd be happy to work on a pull request if we can agree on a design. Let me know what you think.