Make SET work with both token and non-token types

[housengw]

Added a destructor variant of SET and changed the signature of SET_ARRAY.
Refer to #65 for details.

The LF tests related to this change are added here: lf-lang/lingua-franca#1097

This PR makes SET work with both token type and non-token types.
This PR also includes changes from #68 since that PR was merged into this PR before merging into main.

[edwardalee]

Let's also change the names to lower case, as suggested, leaving the old names, marked deprecated, for backward compatibility.

[housengw]

From the error message it seems like the lower case set macro is clashing with another function somewhere, probably in included libraries.

/SDKs/MacOSX12.1.sdk/usr/include/c++/v1/istream:163:
    In file included from /Applications/Xcode_13.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk/usr/include/c++/v1/ostream:141:
    /Applications/Xcode_13.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk/usr/include/c++/v1/bitset:703:17: error: too few arguments provided to function-like macro invocation
        bitset& set() _NOEXCEPT;
                    ^
    /Users/runner/work/reactor-c/reactor-c/test/C/src-gen/target/HelloWorldCCPP/ctarget.h:69:9: note: macro 'set' defined here
    #define set(out, val) _LF_SET(out, val)

[Soroosh129]

Looks great! Thanks for cleaning up the C API.

Superficially, should files like ctarget_schedule.h be organized as ctarget/schedule.h instead?

[lhstrh]

Looks great! Thanks for cleaning up the C API.

Superficially, should files like ctarget_schedule.h be organized as ctarget/schedule.h instead?

I've been critical of the move to a separate ctarget_schedule.h because I think it looks weird, but I like your suggestion of having a ctarget/schedule.h. I think that might be a satisfying solution for everybody.

[edwardalee]

This is too big for me to go through in detail right now, but it looks good. What is the plan for updating the tests? Ideally, they all pass unchanged (backward compatibility), but then we update them so that they serve as proper examples. We also need to update the website code and docs.

[housengw]

My plan is to update the tests after merging this PR and lf-lang/lingua-franca#1097.
I will also help with updating the website code.

In regards to Marten's concern, I can do the renaming in a future PR. I think the most time-sensitive actions right now is to get the API out and to update the tests and the website