chore: align thirdparty docs, seq diagrams and oa3 files (mojaloop#362)

Author: kleyow

website/versioned_docs/v1.0.1/api/thirdparty/assets/diagrams/linking/5a-credential-registration.puml

@@ -44,7 +44,6 @@ PISP -> Switch ++: ""PUT /consents/22222222-0000-0000-0000-000000000000""\n\
 ""  FSIOP-Source: pispa""\n\
 ""  FSPIOP-Destination: dfspa""\n\
 ""  {""\n\
-    ""  consentRequestId: "11111111-0000-0000-0000-000000000000",""\n\
     ""  status: "ISSUED",""\n\
     ""  scopes: [""\n\
     ""    {""\n\
@@ -86,10 +85,10 @@ rnote over DFSP
 
   If the DFSP opts to use the hub-hosted Auth-Service it then:
   1. Registers the consent with the Auth Service ""POST /consents""
-  2. If the DFSP recieves a  `PUT /consents/{id}` and the callback contains 
-     ""Consent.credential.status"" of ""VERIFIED"", for each scope in the 
-     Consent, the DFSP creates a ""CredentialScope"" else, if it recieves 
-     a `PUT /consents/{id}/error` callback, it knows that the Consent is 
+  2. If the DFSP recieves a  `PUT /consents/{id}` and the callback contains
+     ""Consent.credential.status"" of ""VERIFIED"", for each scope in the
+     Consent, the DFSP creates a ""CredentialScope"" else, if it recieves
+     a `PUT /consents/{id}/error` callback, it knows that the Consent is
      invalid, and can propagate the error back to the PISP
 
 end note
@@ -178,7 +177,6 @@ Auth -> Switch: ""PUT /consents/22222222-0000-0000-0000-000000000000"" \n\
 ""  FSIOP-Source: central-auth""\n\
 ""  FSPIOP-Destination: dfspa""\n\
 ""  {""\n\
-    ""  consentRequestId: "11111111-0000-0000-0000-000000000000"""\n\
     ""  status: "ISSUED",""\n\
     ""  scopes: [""\n\
     ""    {""\n\

website/versioned_docs/v1.0.1/api/thirdparty/assets/diagrams/transfer/1-2-1-agreement.puml

@@ -74,6 +74,7 @@ rnote left of D2 #Light
 ""FSPIOP-Source: dfspa""
 ""FSPIOP-Destination: pispa""
 {
+  "transactionId": "11111111-0000-0000-0000-000000000000",
   "transactionRequestState": "RECEIVED"
 }
 end note