Contributors macro returns inaccurate results and messages

Issue Summary

• The "Contributors macro" macro can be added to pages and blogs to return a list of contributors in a page or space.
• The default options for the macro should return a list of contributors in the page that the macro is added.
• Depending on the when and how the macro is added, the macro either returns the entire space contributors, or "No contributors found".

Steps to Reproduce

Macro added into a new page directly, or via Page template

1. Create a new page and add the "Contributors macro", or use a template with the macro;
   • Contributors for all pages in the Space that the page is in is returned.
2. Publish the page;
   • The message "No contributors found for: authors on selected page(s)" is shown.
3. Refresh the page;
   • The actual page contributor is shown.

Macro added via page template that uses "template variables"

1. Page templates in Confluence supports "variables", which loads a custom editor to prefill the variable values before its parsed to the editor.
2. Create a template and add a "template variables", and the "Contributors macro".
3. Create a page using the template above, and a screen will load to populate the variable.
   • The "Contributors macro" will errors out and returns "Failed to get macro details".
4. Once the variable is added, the same issue for when we add the macro normally is also present.

Expected Results

1. The macro should return the page's contributor on first publish without requiring a page refresh.
2. The macro should not return Space contributors when first added into a page.
3. The macro should return accurate messages when it is not able to fetch the page's contributor.

Actual Results

1. On first publish, the macro returns no contributors and the user will have to refresh the page to see actual contributors.
2. When first added, the macro returns all Space contributors and not the page's contributor.
3. When the macro is used in a template with "template variables", it throws an error, "Failed to get macro details".

Workaround

• Currently there is no known workaround for this behavior. A workaround will be added here when available