Ingest the remaining entities and relationships

[neurovelho]

This PR includes the remaining of the high value entities and relationships as discussed in the issue thread.

Kindly let us know if something needs to be changed.

[neurovelho]

Pinging @aiwilliams @ndowmon @austinkelleher

[neurovelho]

Alrighty, we've implemented the changes you requested @ndowmon.

There's however a few complications though:

• We implemented the user -> assigned -> access token relationship, however it looks like no matter what you do in the dashboard or API, the access tokens simply won't show up in the api/token response -- only the admin tokens do. Sadly this seems like a regular occurrence with this API.

• After trying out multiple things it seems like API only returns repository, build and releaseBundle permissions:

  Release bundle permission is difficult/impossible to implement because they aren’t available during the trial.

  Pipeline permissions can’t seem to be fetched even after we create them in the permission using JFrog admin dashboard, the API simply isn’t returning those for some reason.

  Destination permissions - we aren’t exactly sure what these represent, we don’t see additional field(s) for setting this on the permission setting page nor does the API returns anything about them.

• The pattern matching endpoint can only be used for artifacts, nothing else. That means that when we're matching include/exclude patterns for repositories and builds we pretty much have to use the external library for matching.