feat(cdkDrag): cdkDragExclude to mark a part of the tree as should not be

### Feature Description

Create a Directive (tentatively named cdkDragExclude) that when applied to an element does the effective inverse of cdkDragHandle. That element and it's children will not be able to be dragged/not cause the cdkDrag'ed item to be dragged.

As an alternative to a new directive, It should be possible to accomplish the same goal without adding a new directive by making it so that a cdkDragHandle that's disabled, inside another cdkDragHandle, (or a cdkDrag that's disabled inside another cdkDrag), will result in that element being un-dragable. As it stands, a cdkDrag in a cdkDrag will result in the parent one being moved, and a cdkDragHandle in a cdkDragHandle has no impact. I'm not sure how changing the interactions like that needs to be considered from an API stability point, and I'm also unsure if that's an acceptable option as it is not very intuitive.

### Use Case

This is specifically targeted at parts of a component/component tree that have interactive elements of their own. (or where one might wish there to be interactivity)

- Text inputs: Unable to highlight the text on an input with a mouse.
- Text Area: Unable to change the size of a text area input as dragging the anchor in the bottom right corner results in the node moving instead
- Sliders: Sliders become difficult/nearly impossible to use
- Simply Highlighting text: Highlighting text in an element becomes difficult as the node itself will move instead of allowing the text to be selected.

This was discussed previously in #12929 and there was a response of "You can use the cdkDragHandle directive to configure which element should be draggable". The complexity of certain draggable components makes this nearly untenable under some circumstances unfortunately.

If I need to disable dragging on a single sibling element, I have to add cdkDragHandle to all other siblings of that element, all siblings of the element's parent, the parents parent, and so on until I reach the root dragable element itself. That process alone does not account for any margin on the element, which would have to be replaced with margin elements that also have cdkDragHandle, or other such hacks.

This only gets more complicated and unweildly the more elements you have that require disabling of the dragging.

Start by reading the existing cdkDrag and cdkDragHandle directives and the prior discussion in issue #12929. Compare the proposed cdkDragExclude directive with disabled nested handles or drags, then define the API and interaction behavior needed to prevent dragging within excluded elements while preserving normal dragging elsewhere.

Written by the indexing model from the issue text.