Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

When running the tests in an out of tree build directory (here in
scripts/src/), without that fix, we have the following error in
src/samsung-ipc/tests/test-suite.log when running 'make check':
    FAIL: nv_data-md5
    =================

    Traceback (most recent call last):
      File "[...]/scripts/src/tools/../../../tools/nv_data-md5.py", line 69, in <module>
        rc = main()
      File "[...]/scripts/src/tools/../../../tools/nv_data-md5.py", line 64, in main
        nv_data_md5 = NvDataMD5()
      File "[...]/scripts/src/tools/../../../tools/nv_data-md5.py", line 39, in __init__
        self.nv_data_md5 = sh.Command(srcdir + os.sep + 'nv_data-md5')
      File "/usr/lib/python3.9/site-packages/sh.py", line 1342, in __init__
        raise CommandNotFound(path)
    sh.CommandNotFound: ../../../tools/nv_data-md5
    FAIL nv_data-md5.py (exit status: 1)

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Having a code style makes the code easier to read.

As for which code style to use, the code style defined by the
PEP 8 [1] is used in the python standard library and in the main
Python distribution.

Its official nature (it's standardized by python) probably makes it
the most well known and used code style adopted by python programmers.

In it we have a section about string quotes:
    String Quotes
    -------------
    In Python, single-quoted strings and double-quoted strings are the
    same. This PEP does not make a recommendation for this. Pick a rule
    and stick to it. When a string contains single or double quote
    characters, however, use the other one to avoid backslashes in the
    string. It improves readability.

    For triple-quoted strings, always use double quote characters to be
    consistent with the docstring convention in PEP 257.

Since "if __name__ == '__main__':" is widely used, we choose to use the
single quotes.

[1]https://www.python.org/dev/peps/pep-0008/

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>