Use on_load module attribute

Before OTP 19.0, if the on_load directive fails, any previously loaded
code would become old, essentially leaving the system without any
working and reachable instance of the module. This is not true anymore
since OTP 19.0, so loading the nifs within the on_load directive is
today the cleanest and best code pattern.

It seems indeed very convoluted to have an entire application and
supervision tree with a worker gen_server just to load the nifs. Also,
one of the `handle_info` heads of the gen_server is even a remnant of
the times when `fast_tls` was implemented as a port driver instead of as
nifs, which is a high sign this needed some modernisation.

Author: NelsonVides

src/stringprep.app.src

@@ -26,7 +26,6 @@
   {modules,      []},
   {registered,   []},
   {applications, [kernel, stdlib, p1_utils]},
-  {mod,          {stringprep_app,[]}},
 
   %% hex.pm packaging:
   {files, ["src/", "c_src/stringprep.cpp", "c_src/uni_data.c", "c_src/uni_norm.c", "configure", "rebar.config", "rebar.config.script", "vars.config.in", "README.md", "LICENSE.txt", "LICENCE.ALL", "LICENSE.TCL"]},

src/stringprep.erl

@@ -22,13 +22,13 @@
 %%%----------------------------------------------------------------------
 
 -module(stringprep).
+-on_load(load_nif/0).
+-nifs([tolower/1, tolower_nofilter/1, nameprep/1, nodeprep/1, resourceprep/1]).
 
 -author('[email protected]').
 
--compile(no_native).
-
--export([start/0, load_nif/0, tolower/1, nameprep/1,
-	 nodeprep/1, resourceprep/1, tolower_nofilter/1]).
+-export([start/0, tolower/1, nameprep/1,
+         nodeprep/1, resourceprep/1, tolower_nofilter/1]).
 
 %%%===================================================================
 %%% API functions