check_submission_allowed messages all have the same severity

[khattam2]

Fixes #1226

Description

What?

check_submission_allowed messages all have the same severity

Why?

submission_check is given a flag whether it should print the strings as errors or warnings but this does not make sense

How?

The flag has been removed and severity is decided by the statement.

Testing

Remember to add or update unit tests for new features and changes.

• How to test your changes in A-plus
• How to test accessibility

What type of test did you run?

• [ ] Accessibility test using the WAVE extension.
• [ ] Django unit tests.
• [ ] Selenium tests.
• [ ] Other test. (Add a description below)
• [ ] Manual testing.

[ADD A DESCRIPTION ABOUT WHAT YOU TESTED MANUALLY]

Did you test the changes in

• [ ] Chrome
• [ ] Firefox
• [ ] This pull request cannot be tested in the browser.

Think of what is affected by these changes and could become broken

Translation

• [ ] Did you modify or add new strings in the user interface? (Read about how to create translation)

Programming style

• [ ] Did you follow our style guides?
• [ ] Did you use Python type hinting in all functions that you added or edited? (type hints for function parameters and return values)

Have you updated the README or other relevant documentation?

• [ ] documents inside the doc directory.
• [ ] README.md.
• [ ] Aplus Manual.
• [ ] Other documentation (mention below which documentation).

Is it Done?

• [ ] Reviewer has finished the code review
• [ ] After the review, the developer has made changes accordingly
• [ ] Customer/Teacher has accepted the implementation of the feature

Clean up your git commit history before submitting the pull request!

[ihalaij1]

This PR requires some more changes to correctly classify and display error/warning/info messages from functions one_has_submissions() and one_has_access().

I will be making these changes myself.