Couldn't parse org rules

[ekievsky]

This PR tolerates not found, timeout, service unavailable errors in EnterpriseService;

close #408

---

Tests:

• Does not need tests

---

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

• addresses the issue it closes (if any)
• code is readable and understandable
• is accompanied with tests, or tests are not needed
• is free of vulnerabilities
• is documented clearly and usefully, or doesn't need documentation

[tomholub]

-> did I receive a response and it's other status 4xx or 5xx? -> show error to user

Where was this implemented?

-> did I NOT receive a response (server down or timeout) and the internet is otherwise working? -> don't use FES, empty OrgRules

Where was this implemented?

-> did I NOT receive a response (server down or timeout) and the internet is not working? -> show error to user

Where was this implemented?

---

This PR only addresses 20% of the requirements that were clearly laid out in the issue. If the PR addresses less then all requirements of an issue, you must clearly highlight which parts you addressed, and don't close the issue in the PR description.

[tomholub]

Should also tolerate the following, which all are related to server down

  kCFURLErrorCannotConnectToHost    = -1004,
  kCFURLErrorNetworkConnectionLost  = -1005,
  kCFURLErrorDNSLookupFailed        = -1006,
  kCFURLErrorHTTPTooManyRedirects   = -1007,
  kCFURLErrorResourceUnavailable    = -1008,

[tomholub]

Also, what is the number 100 here, 100 seconds? Milliseconds?

[ekievsky]

for some reason my lates commit wasn't included :/