Update Security Level Configuration via Script

[ryan.white]

Regarding library scripts:

@pturmel

The reasons are, to start:

• Functions in the project library are re-usable. When carefully designed, they can be used in many parts of your application.
• Functions in the project library can re-use constants and cached values that are stored in named variables outside the def. This does reduce execution time, as those variables persist from call to call.
• Functions in the project library are maintenance-friendly, particularly that they are stored in the filesystem in plain text as code.py, and are therefore very friendly to source code control, like git.

The 2nd point is especially important when using system.net.httpClient, where you want to be reusing the same instance as much as possible instead of creating a new one each time you do something.

There are also some legacy scoping issues that you get around by having functions defined in the project library script and calling them from events.

Regarding imports:

@pturmel

Be aware that import always takes the interpreter's modules lock

@pturmel

All use of import should be in project library scripts at the outermost level, never inside function definitions, or performance will suffer.

Basically, the trade off between locking once for an import when first initializing the project library script vs locking every time the function is called. Someone else might be able to explain it in further detail.