Update GRID scheme with unique and resolvable URI patterns.

Would suggest to add the following rows toe the GRID schema table at https://un.opensource.unicc.org/unece/uncefact/gtr/docs/Documents/Qualities_of_Registrar_Data

I think it's important that each registrar define a URI for their registry and also a pattern for unique member ID - hence baseline. This brings any register into the modern linked data world by giving every registered entity a globally unique ID. It's a separate (and advanced) question of whether that globally unique member ID is resolvable. There will be a lot of registers that will already have a query endpoint for a member but often that URI pattern will be a consequence of some technical implementation choices and not necessarily what the register would choose as a permanent and unique member ID URI pattern, we need a few URIs here. Eventually they might all converge to one resolver URI pattern that is also the member ID - but for now I think we need some flexibility.

Register ID	string	URI	Baseline	A globally unique ID as a URI that represents this register (eg abr.business.gov.au)
Registered ID Pattern	string	URI	Baseline	A URI template that is used to construct a globally unique and (where possible) resolvable identifier for a registered member of the register (eg given a registered ID 50110219460 and a template abr.business.gov.au/{id} then the globally unique ID for the registered entity is abr.business.gov.au/50110219460). THis may or may not be the same as the query and resolver endpoints below
Query Endpoint	string	URI	Advanced	A URI template for a human readable query about the registered entry (eg https://abr.business.gov.au/ABN/View?abn={id} yielding https://abr.business.gov.au/ABN/View?abn=50110219460
Resolver Endpoint	String	URI	Advanced	Identity resolver service end point per UN identity resolver standard this may or may not be the same as the query endpoint