Workflow improvements with Materials

[justinngan92]

As of v0.1.1, ospgrillage's material module allows users to define materials using codified material properties (e.g. AS5100 or AASHTO standards). The workflow involves a material library of code materials stored in a mat_lib.json file. However the json file is hard coded where any updates/commits on the material library may not be reflected to user's working directory. A workflow conflict occurs between users who wish to: (1) adopt the material library as it is; and (2) adopt and modify certain properties. In hindsight, the following additions should address this and improve the flexibility of material module:

Material module has an internal functionality which creates/stores its material library This is to remove the need to have a local mat_lib.json in the current working directory for the workflow of material module. This internal material library is available to all users and updatable in every release/ commits (e.g. contributors add new materials to the library).

A create_copy_material_json() feature Catering towards users wishing to modify certain properties of material in the library, this feature is needed to create a copy of the internal material library i.e. the mat_lib.json file to the current working directory. From here, users can do edits to this mat_lib.json accordingly.

Material module detecting a local mat_lib.json in the working directory Having created a local mat_lib.json and users edited certain properties, this feature is next needed to for the material module to supercede the internal material library with the locally created/edited mat_lib.json.

Relevent documentations is also required to elaborate this feature in future releases.