Establish consistent construction terminology

[propensive]

We need to build various different things using Soundness APIs. A variety of terms are used for the building process:

• build
• construct
• make
• create and probably others.

The building process may also has several nuances:

• side-effecting operations involved with the creation (e.g. establishing a file on disk)
• allocation of an object
• subsequent or previous operations, often on a mutable value, which help to specify the process
• parsing or other processing
• the potential for exceptions to be thrown

We should audit the current uses of these terms across all libraries, and make them consistent.

[propensive]

Definitions:

• make
  • Abacist
  • Anticipation
  • Capricious
  • Charisma
  • Escapade
  • Galilei
  • Hellenism
  • Kaleidoscope
  • Octogenarian
  • Panopticon
  • Polyvinyl
  • Probably
  • Serpentine
  • Telekinesis
• create
  • Acyclicity
  • Galilei
  • Rudiments
• build
  • Gossamer
  • Nomenclature
  • Polyvinyl
• construct
  • Anticipation
  • Gossamer
  • Quantitative
  • Wisteria