REST: Add ExcludefromDefaultView parameter to /api/v1.0.0/model/fieldsets/{fieldSetId}/{fieldTypeId}

Who would benefit?

Partners and customers working with the data model via REST

What impact would it make?

The Control Center behavior for adding a FieldType to a FieldSet is to automatically set the ExcludeFromDefaultView flag to true on the FieldType in scope. This does not occur with this API method - instead another call needs to be made.
For consistency reasons it would make sense that the behavior is the same.

How should it work?

In order to make this backwards compatible, include a parameter on the FieldType to set the ExcludeFromDefaultView to true or false. Including this parameter should be optional. If the value is the same as what is already in place, it should have no effect.

Why is it needed?

Consistency in behavior and efficiency while working with REST