[PM] Fix A11y issue (2/N)

- If we declare configChanges in AndroidManifest.xml, it avoid the
  activity recreation. Before we use the viewModel design, it may
  have some data not set correctly after the activity is creatected.
  After we use the viewModel design, the data is persisetent. Then,
  the activity can be recreated without setting configChanges and it
  can avoid some unexpected UI issues
- Current design already supports the scroll behavior. Remove the
  setMovementMethod of the custom textview to avoid the a11y issue.
  The custom textview is clickable and long-clickable after setting
  the movementmethod. It causes when the custom textview got the a11y
  focus, the Talkback announces `Double tap to activatee`. But, it
  doesn't have any action after the user clicked it.
- Use " instead of ' in some strings to avoid a11y to announce the
  symbol

Flag: android.content.pm.use_pia_v2
Test: Test it with Talkback
Bug: 437849981
Bug: 437840312
Bug: 438063448
Bug: 420544301

Change-Id: Idf3e287a5d1cda97adbaf7dfb5d1e0bf71ea150f