Update queries to check policy attachment & separation to validate all vs custom iam policies. Fixes #277 Closes #280

[rajlearner17]

Checklist

• cis_v140_1_16 conflict with foundational_security_iam_1 #277
• foundational_security_iam_21 control query name change for better clarity #280

1. foundational_security_iam_1 earlier using iam_policy_no_star_star.sql was not valid, as it was not checking attachment, now it will use query iam_custom_policy_no_star_star.sql which is added with attachment check and restricted to customer managed policies.

2. iam_policy_no_star_star has occurrences in other compliance mods, hence retaining it as is. iam_custom_policy_no_star_star.sql is only used in iam.sp file hence safe.

3. foundational_security_iam_21 , now uses new query iam_custom_policy_no_service_wild_card.sql . Earlier it was using the query iam_custom_policy_no_star_star.sql which was used by foundational_security_iam_1 (mentioned above). As per foundational_security_iam_21 requirement, control checks for service:* pattern.
   (This new query is a single occurrence, safe to proceed)

4. Introduced new query iam_all_policy_no_star_star.sql for cis_v140_1_16 earlier it was using the wrong query i.e. iam_policy_no_star_star.sql (this was again restrictive to the only customer managed and there was no attachment check), cis_v140_1_16 should check all policies inclusive AWS ones which are attached.

[khushboo9024]

Suggested change

	a.arn not like 'arn:aws:iam::aws:policy%'
	a.arn not like 'arn:aws:iam::aws:policy%';