Add documentation around manage.py.

* add simple note on jobs around worker restarts
* Update nautobot/docs/additional-features/jobs.md

Co-authored-by: Glenn Matthews <[email protected]>

…ow (#612)

Since `invoke migrate` is needed prior to `invoke createsuperuser` for a fresh dev install; I have added a *TIP* admonition to the docs in that area to call that out.

Added prefix `NAUTOBOT_` in `override.env` example

See: `docker-entrypoint.sh`

I spent some time troubleshooting an issue running uWSGI directly behind an AWS ALB.  I ran into 502 responses from the ALB for a small percentage of requests under load.  I came across the following issues related to it:

https://medium.com/@gabriel.m.troy/aws-alb-docker-uwsgi-502-bad-gateway-16d0a36f6240
unbit/uwsgi#930
https://www.tessian.com/blog/how-to-fix-http-502-errors/

After much testing the final link from tessian seemed to resolve the issues.  I'm adding a note to the docs here in case anyone else needs to configure uWSGI behind a load balancer.  Based on the fix I'm fairly sure this isn't AWS dependent and it is not well documented on the uWSGI side.  Hoping this note will save someone some time in the future.

1.  The custom field background tasks are now being run in an atomic transaction. 
2. A command `nautobot-server fix_custom_fields` has been added to cleanup objects' custom fields in the case the job has failed.  

Co-authored-by: Jathan McCollum <[email protected]>

…estart (#655)

- This changes the service type for the Celery worker from `forking` to `exec` since we are not actually backgrounding or demonizing the worker processes.
- Also renamed the `pidfile` to `nautobot-worker.pid`.

- This adds a section to the services troubleshooting documentation for a configuration fix when using MySQL and encountering the "incorrect string value" error.

#625)

- Changed Validation Maximum Integer field in CustomFieldModel.
- Added Migration File for the change.
- Added one unit test.

Co-authored-by: Sammy Chafiqui <[email protected]>

- This refactors parsing of network strings to be part of what is now `BaseNetworkQuerySet`
  - `NetworkQuerySet` now inherits from this base, from which `(Aggregate|Prefix)QuerySet` objects inherit 
  - `IPAddressQuerySet` now inherits from this base
- Due to this change `Prefix` and `Aggregate` objects now support an `ip_family` filter and the filter field on each respective filterset (`nautobot.ipam.filters.PrefixFilterSet` & `nautobot.ipam.filters.AggregateFilterSet` have been updated to match
- IPv6 string searching is more robust and can now support queries with or without trailing colons (`:`)

…fixes)

Going through the docs and exploring the new 1.1.0b1 features, I found a few places with bad doc rendering of ordered lists and bullet lists or where some info was outdated/incorrect.