[berkeley-schema] issue template

[mslarae13]

What type of PR is this?

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update
• Content change (Ex- slot or Class name, slot multivalued changes, slot movement from one Class to another, creating a new slot/Class, Enum value changes)
• Informitive change (Ex- descriptions of slots, classes, or enums, removal of unused, commented, or invalid code, updated mappings of terms, classes, or slots to ontologies, added an additional Enum to accommodate new or future metadata)
• changes to ANY files in /src/schema

Description

Provide a description of the PR.e

Issues

No response

Added or Updated tests & example files?

None

If no, why

This is why I have no tests or example files.

Will this change to the schema result in any invalid data?

{"label"=>true}

Will this change to the schema require a migration?

{"label"=>true}

Downstream implications

Examples of downstream changes include any change that requires an update or change to workflows, workflow automation, Postgres ingest, Jupyter notebooks, runtime, & more

Are there any post deployment tasks we need to perform?

No response