ENH: Rename complex to simplnx (#801)

The previous repo would have been at https://www.github.com/bluequartzsoftware/complex

Signed-off-by: Michael Jackson <[email protected]>

.all-contributorsrc

@@ -1,5 +1,5 @@
 {
-  "projectName": "complex",
+  "projectName": "simplnx",
   "projectOwner": "BlueQuartzSoftware",
   "repoType": "github",
   "repoHost": "https://github.com",

.azure/azure-pipelines.yml

@@ -1,10 +1,10 @@
 
 resources:
   repositories:
-  - repository: complex
+  - repository: simplnx
     type: github
     endpoint: BlueQuartzSoftware
-    name: BlueQuartzSoftware/complex
+    name: BlueQuartzSoftware/simplnx
 
 trigger:
   - develop
@@ -58,7 +58,7 @@ jobs:
     displayName: Appending to PATH
 
   - script: |
-      cmake -S $(complex_source_dir) -B $(Build.BinariesDirectory) -G Ninja -DCMAKE_BUILD_TYPE:STRING=$(build_type) -DDREAM3D_DATA_DIR=$(dream3d_data_dir) -C $(Agent.WorkFolder)/NX.cmake -DBUILDNAME:STRING="complex-$(Agent.MachineName)-$(Agent.OS)-PR$(System.PullRequest.PullRequestNumber)"
+      cmake -S $(complex_source_dir) -B $(Build.BinariesDirectory) -G Ninja -DCMAKE_BUILD_TYPE:STRING=$(build_type) -DDREAM3D_DATA_DIR=$(dream3d_data_dir) -C $(Agent.WorkFolder)/NX.cmake -DBUILDNAME:STRING="simplnx-$(Agent.MachineName)-$(Agent.OS)-PR$(System.PullRequest.PullRequestNumber)"
 
     displayName: Configure COMPLEX
 

.clang-tidy

@@ -30,10 +30,10 @@ Checks: "-abseil-*,
   -readability-uppercase-literal-suffix,
   -readability-magic-numbers"
 WarningsAsErrors: '*'
-HeaderFilterRegex: 'complex/.*\.hpp'
+HeaderFilterRegex: 'simplnx/.*\.hpp'
 FormatStyle: file
 CheckOptions:
-  cppcoreguidelines-macro-usage.AllowedRegexp: 'COMPLEX_EXPORT|COMPLEX_NO_EXPORT|COMPLEX_DEPRECATED'
+  cppcoreguidelines-macro-usage.AllowedRegexp: 'SIMPLNX_EXPORT|SIMPLNX_NO_EXPORT|SIMPLNX_DEPRECATED'
   readability-identifier-naming.IgnoreMainLikeFunctions: 'false'
   readability-identifier-naming.PrivateMemberPrefix: 'm_'
   readability-identifier-naming.NamespaceCase: lower_case

.github/ISSUE_TEMPLATE/functionality_report.yml

@@ -19,7 +19,7 @@ body:
     attributes:
       label: Description of the Feature, Filter, or Functionality?
       description: Describe your feature in detail or even provide an implementation plan/existing open source library to reference!
-      value: What if complex had...
+      value: What if simplnx had...
     validations:
       required: true
   - type: dropdown

.github/pull_request_template.md

@@ -1,11 +1,11 @@
 <!-- The text within this markup is a comment, and is intended to provide
-guidelines to open a Pull Request for the complex repository. This text will not
+guidelines to open a Pull Request for the simplnx repository. This text will not
 be part of the Pull Request. -->
 
 
 <!-- See the CONTRIBUTING (CONTRIBUTING.md) guide. Specifically:
 
-Start complex commit messages with a standard prefix (and a space):
+Start simplnx commit messages with a standard prefix (and a space):
 
  * FILTER: When adding a new filter to code 
  * BUG: fix for runtime crash or incorrect result
@@ -29,15 +29,14 @@ close a related issues using keywords (https://help.github.com/articles/closing-
 @mentions (https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
 of the person or team responsible for reviewing proposed changes. -->
 
-
 ## Naming Conventions
 
-Naming of variables should descriptive where needed. Loop Control Variables can use `i` if warranted. Most of these conventions are enforced through the clang-tidy and clang-format configuration files. See the file `complex/docs/Code_Style_Guide.md` for a more in depth explanation.
+Naming of variables should descriptive where needed. Loop Control Variables can use `i` if warranted. Most of these conventions are enforced through the clang-tidy and clang-format configuration files. See the file `simplnx/docs/Code_Style_Guide.md` for a more in depth explanation.
 
 
 ## Filter Checklist
 
-The help file `complex/docs/Porting_Filters.md` has documentation to help you port or write new filters. At the top is a nice checklist of items that should be noted when porting a filter.
+The help file `simplnx/docs/Porting_Filters.md` has documentation to help you port or write new filters. At the top is a nice checklist of items that should be noted when porting a filter.
 
 
 ## Unit Testing
@@ -58,4 +57,4 @@ The idea of unit testing is to test the filter for proper execution and error ha
 - [ ] Classes and methods are properly documented
 
 
-<!-- **Thanks for contributing to complex!** -->
+<!-- **Thanks for contributing to simplnx!** -->