transactional video state changes

changes:
- transactional calls do not need to add
  CallAttributes#SUPPORTS_VIDEO_CALLING in order to initiate
  a video call Or change the video state
- The CallAttributes#CallType is remapped in the
  Outgoing/Incoming-CallTransaction to a VideoProfile value

While investigating transactional video call behavior, I noticed that
the CallAttributes#AUDIO_CALL is remapped to VideoProfile#STATE_TX_ENABLED.
Now, when transactional calls are created, the video value is correctly
mapped to the equalivalent VideoProfile value.

Additionally, the video state changes should not be gatted by the
CallAttributes#SUPPORTS_VIDEO_CALLING. Core-Telecom will not have access
to the new flagged capability so for now, video state changes on a per
call basis will not be gated by that capability.

Flag: com.android.server.telecom.flags.transactional_video_state
Fixes: 335887238 (remap CallAttributes CallType in addCall)
Fixes: 325320195 (do not gate setVideoState with capability)
Test:  4 new unit tests, removed 1 CTS test
Change-Id: I04b030db864e00370e45510670c2e99b6bdfd9ff