Allow hashes in URIs

[srosset81]

Resources are supposed to be identifiable with hashes (like https://mypod.store/alice#me), but SemApps never supported that until now.

To support it, we would need to adapt the ldp.resource.get action to look for hash resources sharing the same main URI. If a hash resource is found, we would need to display it like this in Turtle:

<https://srosset.inrupt.net/profile/card>
  a foaf:PersonalProfileDocument;
  foaf:maker <https://srosset.inrupt.net/profile/card#me>; 
  foaf:primaryTopic <https://srosset.inrupt.net/profile/card#me>.

<https://srosset.inrupt.net/profile/card#me>
    a schema:Person, foaf:Person;
    foaf:name "Sébastien".

And like this in JSON-LD:

{
	"@context": { },
	"@graph": [
		{
			"@id": "https://srosset.inrupt.net/profile/card",
			"@type": "foaf:PersonalProfileDocument",
			"foaf:maker": {
				"@id": "https://srosset.inrupt.net/profile/card#me"
			},
			"foaf:primaryTopic": {
				"@id": "https://srosset.inrupt.net/profile/card#me"
			}
		},
		{
			"@id": "https://srosset.inrupt.net/profile/card#me",
			"@type": [
				"schema:Person",
				"foaf:Person"
			],
			"foaf:name": "Sébastien"
		}
	]
}

WAC permissions are applied for the whole resource.

Left issues

• Will this work with the Fuseki WAC extension ? @nikoPLP
• Will this work with the WAC Moleculer service, notably the webacl.resource.hasRight action ?
• How do we need to adapt the POST/PATCH/PUT actions ?

[srosset81]

Closing as #1265 will solve this problem.