Inventory controllers uses lastCycle, if available, or the first cycle given

[adrian-lara]

Any background context you want to provide?

There were rare cases where the inventory list, inventory map, and pairing pages did not load with a default Cycle.

See the attached issue for more details.

What's this PR do?

Refactors the logic that applies the last Cycle chosen on the inventory list, inventory map, and pairing pages to ensure a Cycle is always chosen.

Before, the logic for applying the last Cycle relied on there existing any "lastCycle" ID (whether or not that ID was for a Cycle known to that Organization). This PR updates that logic to always try to "find" the Cycle associated to the "lastCycle" ID provided before applying it. This validates whether it is, in fact, a Cycle associated to the current organization.

How should this be manually tested?

Go through the steps described in the relevant tickets, and see that a default Cycle is always chosen.
OR alternatively
Manually update the localStorage lastCycle entries to apply a random/invalid Cycle ID to your current org. Then, visit the inventory list, inventory map, or pairing page to see that a default Cycle is chosen regardless of that invalid ID.

What are the relevant tickets?

#2069

[coveralls]

Coverage remained the same at 76.473% when pulling f2dc102 on 2069_default_cycle into 080ba83 on develop.

[nllong]

Tested on inventory, map, and pairing by resetting localStorage cycles. Worked as expected.