[Spike] Move/Remove Appointments Preferences API endpoint

[JunTaoLuo]

Background/Request

As part of our zero silent errors I noticed that we are not using the PreferenceService that is exposed as an endpoint in our BE. However, it is used by the mobile team here. This issue tracks the work to either move this logic into mobile or remove this endpoint.

Goal

• We want to determine what to do with the appointments preference API endpoint given that we don't use it. This includes the service, controller and associated tests. Currently I see three options
  • Keep it in VAOS module: this would make sense if we plan to use this endpoint ourselves in the future
  • Move it from VAOS module to mobile module: this makes sense if mobile uses this endpoint and we don't
  • Remove it completely: this makes sense if neither us nor mobile uses this endpoint

Requirements to Consider

• If we remove the endpoint from VAOS module, do we need to deprecate the endpoint before removing it in case some team somewhere used it in the past?

Tasks

• Answer the following questions:
  • [ ] Reach out to the mobile team and see if they are actively using the PreferencesService
  • [ ] Determine which of the three proposed options listed above to take or propose an alternative approach

Time Box

_ hours

Definition of Done

• Tasks are complete
• Research and recommendations are documented in this ticket

[Bren22va]

Hey team! Please add your planning poker estimate with Zenhub @cferris32 @jenniemc @JunTaoLuo @ryanshaw @simiadebowale @vbahinwillit