[WIP] Lots of test refactoring (#1042)

* make behave slightly less verbose for use with behave --format progress2
* standardize behave tests
* move tests around to be more behavior driven
* clean up txt file after tests
* add more tests, add more functionality to behave for calling mock editor
* move around behave tests, get rid of regression files
* clean up some code around keyrings
* add more placeholder test scenarios (marked with @todo)
  You can run just these tests with `behave --no-skipped --tags=todo`
* fix "missing_directory" test
  This test was missing the config file it was trying to use. So, it was
  really a very useless, broken test that we absolutely should not have
  approved the PR (#963) for.
* add write tests for each journal type
* update version tests, add new regex match behave step
* add config test outlines
* add journal types to some search tests
* change "basic" config reference to "simple"
* update configs
* add more journal types in search
* fix basic folder journal reference
* add flush output steps to behave, update delete flag tests
* fix failing test with a flush
* update more delete flag tests to include other journal types
* fix file cleanup after failed test with no debug on
* fix password test
* fix DayOne tag sample data, move search/format tag tests, and run them on multiple jrnl types
* added ability to auto-prompt for password for encrypted journals
  Only uses password when prompted, and doesn't get in the way of other
  input prompts. This allows us to run the same scenarios on both
  encrypted journals and other journal types.
* fold encrypted scenarios into the rest of the scenarios where possible
* remove apostrophe that is breaking tests on CI
* add more journal type tests to import feature
* standardize whitespace in behave tests, take out duplicate test
* update handling of cache directories in test suite (easier syntax)
* skip failing YAML exporter emoji test on Windows
* added @todo tags for things that need follow-up

Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>

features/file_storage.feature

@@ -0,0 +1,46 @@
+Feature: Journals iteracting with the file system in a way that users can see
+
+    Scenario: Adding entries to a Folder journal should generate date files
+        Given we use the config "empty_folder.yaml"
+        When we run "jrnl 23 July 2013: Testing folder journal."
+        Then we should see the message "Entry added"
+        When the journal directory is listed
+        Then the output should contain "2013/07/23.txt" or "2013\07\23.txt"
+
+    Scenario: Adding multiple entries to a Folder journal should generate multiple date files
+        Given we use the config "empty_folder.yaml"
+        When we run "jrnl 23 July 2013: Testing folder journal."
+        And we run "jrnl 3/7/2014: Second entry of journal."
+        Then we should see the message "Entry added"
+        When the journal directory is listed
+        Then the output should contain "2013/07/23.txt" or "2013\07\23.txt"
+        Then the output should contain "2014/03/07.txt" or "2014\03\07.txt"
+
+    Scenario: If the journal and its parent directory don't exist, they should be created
+        Given we use the config "missing_directory.yaml"
+        Then the journal should not exist
+        When we run "jrnl This is a new entry in my journal"
+        Then the journal should exist
+        When we run "jrnl -n 1"
+        Then the output should contain "This is a new entry in my journal"
+        And the journal should have 1 entry
+
+    Scenario: If the journal file doesn't exist, then it should be created
+        Given we use the config "missing_journal.yaml"
+        Then the journal should not exist
+        When we run "jrnl This is a new entry in my journal"
+        Then the journal should exist
+        When we run "jrnl -n 1"
+        Then the output should contain "This is a new entry in my journal"
+        And the journal should have 1 entry
+
+    Scenario: Creating journal with relative path should update to absolute path
+        Given we use the config "missingconfig"
+        When we run "jrnl hello world" and enter
+        """
+        test.txt
+        n
+        """
+        And we change directory to "features"
+        And we run "jrnl -n 1"
+        Then the output should contain "hello world"