Instead of making the send buffer size super small, just do a sleep when
sending data to simulate the inability to send out as much data as
desired.

The delete operator can be called on a null pointer, so there's no
reason for these tests.

Usually if you are reconnecting after network outage, it will give a
different code (such as OBS_OUTPUT_CONNECT_FAILED).  So, if already
reconnecting, ignore the code unless it's OBS_OUTPUT_SUCCESS.

Update and rename nb-NO to nb-NO.txt

Now with a proper file extension.
Fixed a line I forgot to add the translation for.

I was tired when I sent the pull request, okay?!

Norwegian (bokmål) translation

Update fi.txt

Portuguese (Portugal) Translation.

Fixed an Error

Portuguese translation, used latest EN file as a base.

Fixes a bug where it would use the max retries for the delay time and
vise-versa.

Because: why not?

I was implementing a pushing/popping attributes function like with GL,
but I realized that for our particular purposes (and actually for most
purposes) its usage was somewhat..  niche.  I may still implement
pushing/popping of attributes in the future, though right now I feel
using a function to reset the state is sufficient for our purposes.

Implement recent property and data changes for win-dshow

Update de.txt

Fixed some typos and missing commas.

There was no need to call the context free function in the
initialization function, and it's safer to just initialize the memory to
0 before using (which also negates the need for da_init)

This just ensures that if an obs object is renamed that the pointer to
older names will still be valid.  Prevents renames from causing any
invalid memory access.

When the obs object is destroyed, so are the cached names.

The core itself now provides reconnection options (enabled by default, 2
second timeout between reconnects, 20 retries max until actual
disconnection occurs).  This will make things easier for both module
developers and UI developers.

Reconnecting treats the stream as though it were still active, and
signals are sent when reconnecting and upon successful reconnection.

Need to implement user interface information for reconnections.

Autoselection is only implemented for frame rate as it doesn't make
sense to autoselect the video format (Any fills the role of library
supplied autoselection) or the resolution (it may make sense to
implement resolution matching based on the current transformation
settings in the future though)

Use warn/info/debug helper macro functions to output
warnings/information/debug log data that's preformatted to include the
module and the current output name.