Introduce sector module

[stap-m]

Summary of the discussion

#1399
In this PR, the new sector module is generated and populated with all sectors, sector divisions and many sector individuals which originally lived in oeo-social.

Type of change (CHANGELOG.md)

Added

• Added a new module oeo-sector.omn

Updated

• move sector and sector division and subclasses to the new module

Workflow checklist

Automation

Closes #

PR-Assignee

• 🐙 Follow the Pull Request Workflow
• 📝 Update the CHANGELOG.md
• 📙 Add #'s to term tracker item

Reviewer

• 🐙 Follow the Reviewer Guide
• 🐙 Provided feedback and show sufficient appreciation for the work done

[stap-m]

I tried out several things and took a595d17 as template, but it the new module seems not to be recogized when I import it to oeo-shared-axioms. @areleu @l-emele @MGlauer any ideas what the problem is?

[l-emele]

In file src/ontology/edits/catalog-v001.xml you have now both an Import Wizard Entry and an User Entered Import Resolution:

    <uri id="Imports Wizard Entry" name="http://openenergy-platform.org/ontology/oeo/dev/oeo-sector.omn" uri="oeo-sector.omn"/>
    <uri id="User Entered Import Resolution" name="http://openenergy-platform.org/ontology/oeo/dev/oeo-sector.omn" uri="oeo-sector.omn"/>

Maybe that is causing the problem?

Additionally, I noticed that when I open oeo.omn in your current branch, Protégé adds an additional entry into src/ontology/catalog-v001.xml

    <uri id="User Entered Import Resolution" name="http://openenergy-platform.org/ontology/oeo/dev/oeo-sector.omn" uri="edits/oeo-sector.omn"/>

[l-emele]

I did not check commit by commit, but the overall changes in Protégé look fine.

I found one problem regarding some sector individuals. However this problem occurs not only in the feature branch of this PR but also in dev, so it was not introduced by this PR. Thus I created issue #1730