[TASK] Version 3.2 release

[j-bryan]

---

Issue Description

Reference issue for creating a RAVEN 3.2 release.

Version number should be incremented to 3.2 in setup.py to mark the new release.

Some minor issues have been identified requiring some fixes in order to build the pip packages and to have them pass the RAVEN test suite. Issues identified so far:

• "raven_framework" executable not found by ravenframework.Models.Code when test suite is run with option --tester-command RavenFramework /path/to/raven_framework
• Pinned mamba version for macOS causes failed installation with produced .whl file

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• 1. Is it tagged with a type: defect or task?
• 2. Is it tagged with a priority: critical, normal or minor?
• 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• 1. If the issue is a defect, is the defect fixed?
• 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?