Create component responsible for the file system layout of a node

There are a bunch of different important file system locations we currently read and write.

- signed state periodic snapshots
- emergency state dumps
- event streams
- preconsensus event streams (soon)
- temporary files
- keys
- log4j files
- configuration files
- application files (e.g. record stream files, side cars)

Currently, the code defining the locations of these files is scattered all over the place. This makes it hard to maintain and hard to document.

We should create a special component whose only responsibility is to decide the file paths for these types of files. This object should take only node configuration in its constructor, and should have a bunch of methods that return paths.

For example:

```
public class FileSystemLayout {

public FileSystemLayout(final Configuration configuration) {
// ...
}

public Path getSignedStatePath(final long round, final long selfId) {
return Path.of(...);
}

}

```

Start by locating the existing code that defines paths for signed-state snapshots, emergency dumps, event streams, temporary files, keys, logs, configuration, and application files. Trace how node Configuration is provided, then define the component's ownership and verify that each listed location can be obtained through its path methods.

Written by the indexing model from the issue text.