Update copy for when RoSH info can't be retrieved

When RoSH information can't be retrieved, we show guidance to the CPPs
to manually copy the information from Oasys and include it in the
placement consideration risk sections.

However, the guidance for HPTs is for them to manually check outside the
service so they wouldn't know to check that location for the manually
included information.

This change updates the copy in the RoSH section to prompt HPTs to look
in the placement considerations section for this information.

server/form-pages/utils/index.test.ts

@@ -545,7 +545,7 @@ describe('personRisksRoshResponse', () => {
 
     expect(utils.personRisksRoshResponse(risks)).toEqual({
       'Risk of serious harm':
-        'Something went wrong. We are unable to include RoSH information. This risk data must be checked manually outside of this service.',
+        'We were unable to automatically import RoSH information. Check the "Placement considerations" section to find the OASys risk levels. If the risk levels are not present, they must be checked manually outside of this service.',
     })
   })
 })

server/form-pages/utils/index.ts

@@ -274,7 +274,7 @@ export const personRisksRoshResponse = (risks: PersonRisks): PageResponse => {
   }
   return {
     'Risk of serious harm':
-      'Something went wrong. We are unable to include RoSH information. This risk data must be checked manually outside of this service.',
+      'We were unable to automatically import RoSH information. Check the "Placement considerations" section to find the OASys risk levels. If the risk levels are not present, they must be checked manually outside of this service.',
   }
 }