Bluetooth: CCC values should be treated as bitfields

[alwa-nordic]

See #80988 (comment).

A CCC value is a bitfield. When testing for BT_GATT_CCC_NOTIFY and BT_GATT_CCC_INDICATE, & should be used instead of ==.

This issue is about all misuses like this. Some may be benign, but this issue is labeled 'bug' because it's likely some instances may be a bug that can be triggered in a multiple connection scenario.

More info the comment thread linked above. This issue is to be refined.

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.