Added Model for SIGs

[imApoorva36]

Description

Added model for SIGs

Fixes # (issue)

Dependencies

None new

Type of Change

What types of changes does your code introduce?
Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration. (for bug fix / breaking change)
Put an x in the boxes that apply

• Test A
• Test B

---

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[anirudhprabhakaran3]

Move the model to the pages app.

[nishant-nayak]

For making any DB related changes, I would highly recommend you check out the ER Diagrams in the wiki. I've documented the fields required, the type of the field and any DB constraints that we should apply.

For this case, the SIG model should go in the config app, alongside the Society model.

[anirudhprabhakaran3]

Aah yes, my bad. I didn't check the ER diagram before commenting that 😓

[anirudhprabhakaran3]

Delete all the migration files, and create one single migration file.

[anirudhprabhakaran3]

Bruh wait, we need to figure out how to restore those migrations you've deleted.