Port the wasi-filesystem API to the new wai format. #35

This makes a number of changes, to make use of interface-types features such
as expected, variant types, and resources. The change to use resources in
particular means that filesystem functions are now methods of the descriptor
resource. Since this means renaming everything, take this opportunity to
introduce a new naming conventions, with _at being used for functions that
take dirfd+path arguments.

This also eliminates the rights concept what was present in earlier versions
of WASI, has has discussed in #31. This required adding new flags to open_at,
so while here, this also adds basic chmod-like support, as discussed in #33.

And, this removes support for readdir seeking (seekdir/telldir), as discussed
in #7.

And it adds a fifo file type and a more general socket type, as discussed in #4.

README.md

@@ -0,0 +1,110 @@
+# [Example WASI proposal]
+
+This template can be used to start a new proposal, which can then be proposed in the WASI Subgroup meetings.
+
+The sections below are recommended. However, every proposal is different, and the community can help you flesh out the proposal, so don't block on having something filled in for each one of them.
+
+Thank you to the W3C Privacy CG for the [inspiration](https://github.com/privacycg/template)!
+
+# [Title]
+
+A proposed [WebAssembly System Interface](https://github.com/WebAssembly/WASI) API.
+
+### Current Phase
+
+[Fill in the current phase, e.g. Phase 1]
+
+### Champions
+
+- [Champion 1]
+- [Champion 2]
+- [etc.]
+
+### Phase 4 Advancement Criteria
+
+TODO before entering Phase 2.
+
+## Table of Contents [if the explainer is longer than one printed page]
+
+- [Introduction](#introduction)
+- [Goals [or Motivating Use Cases, or Scenarios]](#goals-or-motivating-use-cases-or-scenarios)
+- [Non-goals](#non-goals)
+- [API walk-through](#api-walk-through)
+  - [Use case 1](#use-case-1)
+  - [Use case 2](#use-case-2)
+- [Detailed design discussion](#detailed-design-discussion)
+  - [[Tricky design choice 1]](#tricky-design-choice-1)
+  - [[Tricky design choice 2]](#tricky-design-choice-2)
+- [Considered alternatives](#considered-alternatives)
+  - [[Alternative 1]](#alternative-1)
+  - [[Alternative 2]](#alternative-2)
+- [Stakeholder Interest & Feedback](#stakeholder-interest--feedback)
+- [References & acknowledgements](#references--acknowledgements)
+
+### Introduction
+
+[The "executive summary" or "abstract". Explain in a few sentences what the goals of the project are, and a brief overview of how the solution works. This should be no more than 1-2 paragraphs.]
+
+### Goals [or Motivating Use Cases, or Scenarios]
+
+[What is the end-user need which this project aims to address?]
+
+### Non-goals
+
+[If there are "adjacent" goals which may appear to be in scope but aren't, enumerate them here. This section may be fleshed out as your design progresses and you encounter necessary technical and other trade-offs.]
+
+### API walk-through
+
+[Walk through of how someone would use this API.]
+
+#### [Use case 1]
+
+[Provide example code snippets and diagrams explaining how the API would be used to solve the given problem]
+
+#### [Use case 2]
+
+[etc.]
+
+### Detailed design discussion
+
+[This section should mostly refer to the .wai.md file that specifies the API. This section is for any discussion of the choices made in the API which don't make sense to document in the spec file itself.]
+
+#### [Tricky design choice #1]
+
+[Talk through the tradeoffs in coming to the specific design point you want to make.]
+
+```
+// Illustrated with example code.
+```
+
+[This may be an open question, in which case you should link to any active discussion threads.]
+
+#### [Tricky design choice 2]
+
+[etc.]
+
+### Considered alternatives
+
+[This section is not required if you already covered considered alternatives in the design discussion above.]
+
+#### [Alternative 1]
+
+[Describe an alternative which was considered, and why you decided against it.]
+
+#### [Alternative 2]
+
+[etc.]
+
+### Stakeholder Interest & Feedback
+
+TODO before entering Phase 3.
+
+[This should include a list of implementers who have expressed interest in implementing the proposal]
+
+### References & acknowledgements
+
+Many thanks for valuable feedback and advice from:
+
+- [Person 1]
+- [Person 2]
+- [etc.]

test/README.md

@@ -0,0 +1,11 @@
+# Testing guidelines
+
+TK fill in testing guidelines
+
+## Installing the tools
+
+TK fill in instructions
+
+## Running the tests
+
+TK fill in instructions