Add ability to build in publish directory, and concurrent builds

[lainets]

Description

What?

• Add ability to build in publish directory for speed.
• Build separate courses concurrently

Why?

To speed up the build

How?

• Checkbox in course options to bybass the multitiered build folder system to directly build in publish folder.
• Lock the build function separately for each course

Fixes #21

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)
• [X] Manual testing.

Checked that you can build courses concurrently and that only one build will run per course. Checked that course worked even with the bypass enabled.

Did you test the changes in

• [ ] Chrome
• [ ] Firefox
• [x] 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.
• [x] 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

[lainets]

Made this beforehand for when the testing on minus is done.

[markkuriekkinen]

I forgot to say this. It looks like the exclude_patterns setting in apps.meta is not taken into account in the first build after pushing changes to apps.meta. The subsequent builds do take it into account.

[lainets]

I forgot to say this. It looks like the exclude_patterns setting in apps.meta is not taken into account in the first build after pushing changes to apps.meta. The subsequent builds do take it into account.

This is true, and due to the fact that the setting comes from the git repo but we need that setting before the git repo is updated. We could checkout that specific file first but I figured it doesn't matter as that setting shouldnt be required for the course build anyway (the first build will never have any extra files that would be removed)