[webauthn] adopt consistent terms for RP server-side and client-side components

equalsJeffH has just created a new issue for 
https://github.com/w3c/webauthn:

== adopt consistent terms for RP server-side and client-side 
components ==
We use the terms `script`, `a script`, `the script`, `scripts`, 
`browser script`, `javascript`, `WebAuthn Relying Party script`, 
`WebAuthn Relying Party client-side app`, `the client-side app`, `RP’s
 client-side app`, and `the WebAuthn Relying Party client-side 
application` to refer to the same **RP client-side component**.  

We use the terms `the server`, `server`, `servers`, and `WebAuthn 
Relying Party’s server` to refer to the same **RP server-side 
component**. 

We should decide on one consistent series of terms (and acronyms, as 
appropriate) to cover all the necessary semantic bases. 

some ideas: 

[ Note: " {....}" denotes optionality and possibly use of acronyms 
such as "RP", "RP's", "RPs". ]

client-side:   {  [[RP]] | [[RPS]]  }  script    // plus create 
glossary entry and clearly equate to "WebAuthn Relying Party's 
client-side webapp component" (or unambiguous equivalent).  

server-side:  {  [[RP]] | [[RPS]]  }  server   // plus create glossary
 entry and clearly equate to "WebAuthn Relying Party's server-side 
webapp component" (or unambiguous equivalent).  



Please view or discuss this issue at 
https://github.com/w3c/webauthn/issues/80 using your GitHub account