Make apex_entity_url relative

@sokru thank you for creating this issue.

I am having trouble reproducing this as a problem. The apex entity url matches (at least in all my uses) matches the full url of the site the report is run on. It does this so that if anyone exports the report to a CSV, the export gives all the info needed. If it used relative links, they would be useless in the CSV.

When I run the report on my local sandbox, I get links to the local sandbox. When I run the report on prod, I get links to prod.

I think the issue of the lower environment links pointing to prod only comes up when you copy the database from one environment to another and then do not re-run the report.

To solve this issue we would need to drop the audit table after a database copy happens. Maybe a cron that looks at the first row in table to see if the urls match the current site, and if not, drops the table.

I think the simplest solution would be to convert relative paths to absolute URL's only when exporting the csv-file.

@sokru that sounds like a good solution.

Just an FYI from when I was getting reports like this -- if you start converting between absolute and relative you may then run into "excitement" on sites that are served from a subfolder.